Brian Dessent wrote:
[snip]
> If I understand this right you can safely comment out the above check
> without affecting much of anything, just to shut up gdb. Or you can try
> "handle SIGSEGV nostop, noprint, pass". But then you'd miss a
> legitimate SEGV -- I don't know if that's what you're try
René Berber wrote:
> - From what you said, the "initializer=0x0" is what casuses the SIGSEGV.
I'm not sure if that's what's causing it, because it doesn't try to
dereference that. I think what's happening is that this:
/* The opengroup docs don't define if we should check this or not,
bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Dessent wrote:
[snip]
> You can ignore that. Just type "continue" and things will work fine.
> There is probably a way you instruct gdb to automatically ignore this
> but I don't know what it is off the top of my head.
Thanks! Using continue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
[snip]
> (I, for one, won't be very happy if my programs stop working when 1.5.19
> comes out!)
[snip]
Running Scribus with the debug enabled cygqt-mt-3.dll the program works fine
with no mutex failure message and using
On Sat, Dec 10, 2005 at 09:30:27PM -0600, Yaakov S (Cygwin Ports) wrote:
>Ren? Berber wrote:
>>I tried using cygwin1.dll version 1.5.18 and it works just like you said.
>>Then
>>I downloaded the latest snapshot, version 20051207, and scribus fails as
>>before
>>(no error messages, the one I used
René Berber wrote:
> versions of gdb and also Microsoft's WinDbg, all show the same problem
> "Program
> received signal SIGSEGV ... in pthread_key_create". I'll look into this
> tomorrow, I've used gdb under XWindows in HP-UX and Solaris but this is the
> first time under Cygwin/X, perhaps some
===
System Generated Message - DO NOT REPLY TO THIS !
===
PostMaster AvAc has processed the mail detailed below
and has generated this alert for your reference.
Message Details:
