Re: [Help-smalltalk] Crash on sockets and Exceptions

[Holger Hans Peter Freyther]

On 06/13/2011 04:45 PM, Holger Hans Peter Freyther wrote:
> #2  0x00dd434e in abort () at abort.c:92
> #3  0x002a6626 in oldspace_sigsegv_handler (fault_address=0x4, serious=0) at
> oop.c:974
> #4  0x00663b04 in ?? () from /usr/lib/libsigsegv.so.0
> #5  <signal handler called>
> #6  0x002ee41c in copy_semaphore_oops () at interp.c:2431
> #7  _gst_copy_processor_registers () at interp.c:2410
> #8  0x002a899c in copy_oops () at oop.c:1798
> #9  _gst_scavenge () at oop.c:1261
> #10 0x002d6df2 in alloc_new_chunk (numArgs=0, cull_up_to=17) at interp.c:784
> #11 alloc_stack_context (numArgs=0, cull_up_to=17) at interp.c:818
> #12 activate_new_context (numArgs=0, cull_up_to=17) at interp.c:841
> #13 send_block_value (numArgs=0, cull_up_to=17) at interp-bc.inl:428

not the same core (but same backtrace)

(gdb) p sig->data
$4 = (OOP) 0x0
(gdb) p sig->func
$5 = (void (*)(OOP)) 0xa16650 <async_signal_polled_files>

so is IS_OOP(NULL) well defined, giving other code.. I think it is not safe.
So do we add a null check there? or do we use another OOP for aysnc file
notifications?