-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Dessent schrieb: > Ralf Habacker wrote: > >> Running this testcase results in an internal exception in >> pthread_mutexattr_init() >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x610b1005 in pthread_mutexattr_init (attr=0x404040) at >> ../../../../src/winsup/cygwin/thread.cc:129 >> 129 if ((*object)->magic != magic) > > Sigh. We've been through this ad nauseum in the archives. This is how > it's supposed to work, there's nothing wrong here.
But in the case of pthread_mutexattr_init() this exception results in an abort of pthread_mutexattr_init(), which should not be. See my other mail in this thread. > Gdb doesn't know any > better though, and reports it as a SIGSEGV, when it is not. Did you not > notice that when you run the program outside of the debugger it does not > fault? There is no segfault, but it does not work as expected e.g. pthread_mutexattr_init() does not fill the pthread_mutexattr_t struct given as parameter. If you use a recent Cygwin snapshot and a gdb built from CVS you > see no such fault, because this defect in gdb has been fixed. > Ralf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEdCDRoHh+5t8EXncRAkcSAJ0TpZMnh5qhSQKY8nrb688Pq4bxogCfaTG5 9LDqWxCYGtlpmm9LBrKZcac= =2syh -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/