This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.5.19: changes have broken Qt3
- From: Ralf Habacker <ralf dot habacker at freenet dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 23 May 2006 20:13:24 +0200
- Subject: Re: 1.5.19: changes have broken Qt3
- References: <044e01c67e8f$0abed720$a501a8c0@CAM.ARTIMI.COM>
-----BEGIN PGP SIGNED MESSAGE-----
Dave Korn schrieb:
> On 23 May 2006 18:10, Ralf Habacker wrote:
> Oh no, not this old saw again!
>> mutex1n | grep C0000005
>> - --- Process 4872, exception C0000005 at 610B1005
>> 155 78759 [main] mutex1n 4872 _cygtls::handle_exceptions: In
>> cygwin_except_handler exc 0xC0000005 at 0x610B1005 sp 0x22CC00
> [ snip many more ].
>> I identified the problem to the function pthread_mutexattr_init address
>> 0x610b1005 in which a null pointer (%eax below) causes this seg fault
> Yes, but it's wrapped in an exception handler. That's why you get to see an
> strace error message, rather than having the process exit. Names like
> "cygwin_except_handler" and "_cygtls::handle_exceptions" should have given you
> some clues about this
Hmmh, I have learned to fix obviously problems instead let it handle by
an exception handler, which has several disadvantages.
1. It costs additional runtime. In the mentioned designer i count 1653
internal exceptions, which are caused by the null pointer issue.
2. 70% of my strace output (1000 lines) are polluted by this internal
exceptions messages, which could be avoided by changing only on lines of
code. Do you think that this is the effort worth ?
Are there more problems with this simple patch ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html