I cannot reproduce a simple testcase because the app is really big.
I'll try to find the problem but it is really hard.
Is there a way to simple use pthreadwin32 with cygwin? I found no info
about that and there are a lot of conflicts when compiling using
pthreadwin32.
Giuseppe
>
> If you can p
Pavel Tsekov wrote:
On Fri, 16 Dec 2005, Christopher Faylor wrote:
On Fri, Dec 16, 2005 at 02:10:31PM +0100, Pavel Tsekov wrote:
i'm using cygwin release version is 1.5.18-1 and my program compiles
and work perfectly on linux. It compiles also on cygwin but after
15-20 sec it segfault. I t
On Fri, 16 Dec 2005, Christopher Faylor wrote:
> On Fri, Dec 16, 2005 at 02:10:31PM +0100, Pavel Tsekov wrote:
> >>>i'm using cygwin release version is 1.5.18-1 and my program compiles
> >>>and work perfectly on linux. It compiles also on cygwin but after
> >>>15-20 sec it segfault. I think tha
On Fri, Dec 16, 2005 at 02:10:31PM +0100, Pavel Tsekov wrote:
>>>i'm using cygwin release version is 1.5.18-1 and my program compiles
>>>and work perfectly on linux. It compiles also on cygwin but after
>>>15-20 sec it segfault. I think that the problem is in pthread
>>>implementation on cygwin.
> > i'm using cygwin release version is 1.5.18-1 and my program compiles
> > and work perfectly on linux.
> > It compiles also on cygwin but after 15-20 sec it segfault. I think
> > that the problem is in pthread implementation on cygwin.
>
> The cygwin pthread implementation is guaranteed safe
hread implementation is guaranteed safe when used as directed!
> this is stackdump:
>
> 5 [sig] ds2 1944 handle_threadlist_exception:
> handle_threadlist_exception called with threadlist_ix -1
> Exception: STATUS_ACCESS_VIOLATION at eip=61015EF1
>
> please explain me if it&#x
ption:
handle_threadlist_exception called with threadlist_ix -1
Exception: STATUS_ACCESS_VIOLATION at eip=61015EF1
please explain me if it's possibile to fix it.
thanks,
Giuseppe A.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/pro
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 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 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 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 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, 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:
> 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 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, 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
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
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
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
19 matches
Mail list logo
