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

[Holger Hans Peter Freyther]

On 04/14/2011 08:38 AM, Paolo Bonzini wrote:
> On Wed, Apr 13, 2011 at 18:12, Holger Hans Peter Freyther
> <address@hidden> wrote:
>> I have attached the GDB backtrace and the two variables from frame 3 that
>> decide that we end up in the abort. I have also the strace output.
>>
>> do you have any idea of what is going wrong?
> 
> How many sockets are open?  In any case, the simplest thing is to
> register the signal handler itself as an async call (a kind of "bottom
> half") so that the signals can then be done synchronously.

I might have multiple instances of 'Socket' around (I should add them to the
finalizer list to have close called) but only _one_ should be connected.


> 
> 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?