Anyone else seeing quite a lot of these with current cvs HEAD? Often when
pressing Ctrl-C, sometimes when things exit for other (signal-related?)
reasons?
I think this error indicates that a signal has been received but either
find_tls hasn't yet been called, or something has overwritten th
On Thu, 1 Sep 2005, Christopher Faylor wrote:
> On Thu, Sep 01, 2005 at 03:25:17PM +0100, Dave Korn wrote:
> >
> > Anyone else seeing quite a lot of these with current cvs HEAD? Often when
> >pressing Ctrl-C, sometimes when things exit for other (signal-related?)
> >reasons?
> >
> > I think thi
On Thu, Oct 06, 2005 at 04:18:39PM +0300, Pavel Tsekov wrote:
>On Thu, 1 Sep 2005, Christopher Faylor wrote:
>
>> On Thu, Sep 01, 2005 at 03:25:17PM +0100, Dave Korn wrote:
>> >
>> > Anyone else seeing quite a lot of these with current cvs HEAD? Often when
>> >pressing Ctrl-C, sometimes when thin
On Thu, 6 Oct 2005, Christopher Faylor wrote:
> Did you happen to notice when the age of the message to which you're
> responding? Dave figured out the problem subsequent to sending the
> above. It was due to some object files not getting rebuilt after a
> change to cygtls.h.
Yes. When I saw t
On Thu, Oct 06, 2005 at 05:39:35PM +0300, Pavel Tsekov wrote:
>On Thu, 6 Oct 2005, Christopher Faylor wrote:
>
>> Did you happen to notice when the age of the message to which you're
>> responding? Dave figured out the problem subsequent to sending the
>> above. It was due to some object files no
On Thu, 6 Oct 2005, Christopher Faylor wrote:
> >It might be a different problem but the message is the same.
>
> It *is* a different problem.
Ok.
> Some thread is sending a signal 31 (SIGUSR1). Which thread is doing this?
An application thread signaling another thread to stop its execution. I
On Thu, 6 Oct 2005, Pavel Tsekov wrote:
> On Thu, 6 Oct 2005, Christopher Faylor wrote:
>
> > >It might be a different problem but the message is the same.
> >
> > It *is* a different problem.
>
> Ok.
>
> > Some thread is sending a signal 31 (SIGUSR1). Which thread is doing this?
>
> An applicati
On Tue, Oct 11, 2005 at 05:51:00PM +0300, Pavel Tsekov wrote:
>On Thu, 6 Oct 2005, Pavel Tsekov wrote:
>
>> On Thu, 6 Oct 2005, Christopher Faylor wrote:
>>
>> > >It might be a different problem but the message is the same.
>> >
>> > It *is* a different problem.
>>
>> Ok.
>>
>> > Some thread is sen
On Tue, 11 Oct 2005, Christopher Faylor wrote:
> I don't see how ignoring blocked signals would cause a SEGV however.
Well... indirectly they do :) I hope you are not too annoyed already
because this time I really found the cause of the problem.
Assume a signal is sent to a thread with pthread_k
On Wed, 12 Oct 2005, Pavel Tsekov wrote:
> On Tue, 11 Oct 2005, Christopher Faylor wrote:
>
> > I don't see how ignoring blocked signals would cause a SEGV however.
>
> Well... indirectly they do :) I hope you are not too annoyed already
> because this time I really found the cause of the problem.
On Thu, Sep 01, 2005 at 03:25:17PM +0100, Dave Korn wrote:
>
> Anyone else seeing quite a lot of these with current cvs HEAD? Often when
>pressing Ctrl-C, sometimes when things exit for other (signal-related?)
>reasons?
>
> I think this error indicates that a signal has been received but either
Original Message
>From: Christopher Faylor
>Sent: 01 September 2005 15:44
> On Thu, Sep 01, 2005 at 03:25:17PM +0100, Dave Korn wrote:
>>
>> Anyone else seeing quite a lot of these with current cvs HEAD? Often
>> when pressing Ctrl-C, sometimes when things exit for other
>> (signal-rela
12 matches
Mail list logo
