[Mono-devel-list] Debugging infinite loop

Paolo Molaro lupus at ximian.com
Tue Jan 13 14:40:43 EST 2004

On 01/13/04 Jörg Rosenkranz wrote:
> We have the problem that Mono is running into an infinite loop (100% CPU) when calling 
> a static member function of a class using Reflection. This occurs after unloading an 
> AppDomain and creating a new one.
> Do you have any tips to track this issue down? We don't have the Mono Debugger running yet
> and mono --trace doesn't seem to be an option because this happens in our real application
> and the log file would be huge. I was not able to reproduce this in a simple test case.

You can run mono under gdb with:
	gdb /path/to/mono

Inside gdb issue:
	r --debug yourprogram.exe progargs...

When it loops, hit Control-C and then issue (applies the bt command to
all the threads):
	t a a bt

http://www.go-mono.com/jit-debug.html has a couple of suggestons for
finding your way on backtraces that gdb doesn't know about: you should
be able to get a meaningful backtrace even of managed code.

More information about the Mono-devel-list mailing list