Re: [Help-smalltalk] Crashes due the async queue running over

[Holger Hans Peter Freyther]

On 04/14/2011 09:24 AM, Paolo Bonzini wrote:
> On 04/14/2011 09:23 AM, Holger Hans Peter Freyther wrote:
>>> >  The problem is that _gst_async_call must be signal-safe, so it cannot
>>> >  call malloc.
>>
>> Ah okay, this is why we are checking if we are in GST. The question I have
>> is... do we get the SIGIO for the_same_  socket/fd all over again. Can you 
>> see
>> this from the strace or should I inspect the 'bottom half' queue?
> 
> I think you may be getting many SIGIO for the same socket.

Hi Paolo,

do you have any idea? I am not sure if I am trying to cover up a bigger
problem, what about not queuing the call when it is already the last one in
the queue? The other question is why is my kernel sending me SIGIO multiple
times for the same socket?

How to proceed from here?

(gdb) p queued_async_signals_sig[38]
$6 = {func = 0xf71a40 <async_signal_polled_files>, data = 0x0}
(gdb) p queued_async_signals_sig[39]
$7 = {func = 0xf71a40 <async_signal_polled_files>, data = 0x0}
(gdb) p queued_async_signals_sig[40]
$8 = {func = 0xf71a40 <async_signal_polled_files>, data = 0x0}
(gdb) p queued_async_signals_sig[41]
$9 = {func = 0xf71a40 <async_signal_polled_files>, data = 0x0}