David Greene wrote:
Eric Blake wrote:
Read the archives, this issue has already been beaten to death.
This is already fixed in CVS cygwin and CVS gdb; but until cygwin
1.5.20 is released, so that a new gdb snapshot can be provided,
you will have to use snapshots or resign yourself to hitting co
Brian Dessent wrote:
David Greene wrote:
Then please point me to them. My searches didn't turn up
anything.
http://www.google.com/search?q=site:cygwin.com+inurl:ml+inurl:cygwin+pthread+sigsegv+inurl:2006&num=100&filter=0
Thanks for the pointer. I installed the latest cygwin-inst snapshot
Eric Blake wrote:
Read the archives, this issue has already been beaten to death.
This is already fixed in CVS cygwin and CVS gdb; but until cygwin
1.5.20 is released, so that a new gdb snapshot can be provided,
you will have to use snapshots or resign yourself to hitting continue.
When is a n
David Greene wrote:
> Then please point me to them. My searches didn't turn up
> anything.
http://www.google.com/search?q=site:cygwin.com+inurl:ml+inurl:cygwin+pthread+sigsegv+inurl:2006&num=100&filter=0
(and that is only 2006)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> But my program also segfaults in pthread_mutex_init:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x610af064 in pthread_mutex::init () from /usr/bin/cygwin1.dll
Read the archives, this issue has already been beaten to death.
This is already fixed in CVS cygwin and CVS gdb; but unt
Brian Dessent wrote:
David Greene wrote:
Program received signal SIGSEGV, Segmentation fault.
0x610af064 in pthread_mutex::init () from /usr/bin/cygwin1.dll
Please just consult the eleventy-billion previous threads on this
topic. Covered. To. Death.
Then please point me to them. My sear
David Greene wrote:
But my program also segfaults in pthread_mutex_init:
It turns out it also segfaults on pthread_mutex_lock
and pthread_mutex_unlock. Continuing works just fine.
But this is very annoying because the program doesn't
get very far before it has to do a lock or unlock
operation
David Greene wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x610af064 in pthread_mutex::init () from /usr/bin/cygwin1.dll
Please just consult the eleventy-billion previous threads on this
topic. Covered. To. Death.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
Apparently, the saga of pthreads and buggy gdb continues.
I've previously run into the famous gdb pthread_key_create
segfault on IRIX. Apparently it exists on Cygwin as well.
But my program also segfaults in pthread_mutex_init:
Program received signal SIGSEGV, Segmentation fault.
0x610af064 in
9 matches
Mail list logo