[Mono-list] Info request for filing bug report

Dick Porter dick@ximian.com
Thu, 16 Sep 2004 18:09:35 +0100

On Thu, 2004-09-16 at 16:33 +0100, Will Morton wrote:
> 1.  We've just run our .NET application under Linux for the first time, 
> and it ran, out-of-the-box, without any tweaking at all on our part.  
> Our app is about 7000 lines of C# and uses lots of fairly complex 
> threading and networking functionality, so the fact that it Just Works 
> speaks volumes for the stability and usefulness of mono. Our collective 
> thanks and congratulations to all the developers; we'll definitely be 
> contributing to the project once we have some funding and the resulting 
> funds/time. ;o)


> 2.  Mono terminates abnormally when our app closes down, with the 
> following output:
> ** (AvalonShell.exe:31896): WARNING **: : error looking up event handle 
> 0x308
> ** ERROR **: file monitor.c: line 69 (mon_finalize): assertion failed: 
> (mon->wait_list==NULL)
> aborting...
> Aborted

Which version of mono are you using?  If its 1.0, I suggest trying again
with 1.0.1; many bugs were fixed.

>     I'd like to track down the specific event that's causing this 
> failure, so that I can create a test program to submit along with a bug 
> report.  Can anyone assist with what the identity of this 'event handle 
> 0x308', and what .NET call is likely to be causing it?

That message is coming from the internal mono code that emulates w32
system calls.  You can run mono inside gdb and set a breakpoint on
g_logv to catch the assertion failure and get a backtrace.  The event
handle one is a bit harder to pin down.  If you can, try and reproduce
the problem with as small a test case as possible, attach it to a
bugzilla report at http://bugzilla.ximian.com and I can study it.

- Dick