Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81856 --- shadow/81856 2007-07-05 05:15:01.000000000 -0400 +++ shadow/81856.tmp.2931 2007-07-16 07:44:56.000000000 -0400 @@ -132,6 +132,36 @@ database the problem will occur when running in mono. I cannot get the bug to occur with tracing enabled on mono which would suggest to me its going to be hard to reproduce on a different system and is possibly some kind of race. + +------- Additional Comments From [EMAIL PROTECTED] 2007-07-16 07:44 ------- + +More information + +Somebody on irc asked me to append the following +After sending a QUIT signal to mono the following is dumped. + +Full thread dump: +"" tid=0x0xb6e99bb0 this=0x0x60d10: +"" tid=0x0xb7cd8aa0 this=0x0x21e00: + +I am able to trigger this bug on various version of mono / mysql libs. +Mysql Lib tested with are 5.0.3.0 through 5.0.7.0 All of which seem to +cause the same deadlock. + +I have also tested this against mono 1.2.4 and various svn HEAD trees +in the last 2/3 weeks. Last tested against revision 82024 + +I am pritty sure this is not a mysql lib issue as the mono runtime +always locks up. I have tried to use the info on +http://www.mono-project.com/Debugging to attempt to get a stack trace +to look into this issue further but most of the internal functions +stop on mono_domain_lock + +I cannot trigger the deadlock with tracing enabled. +The deadlock does not trigger on windows. Under MS .NET + +Where next ? + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
