[Mono-dev] Logging profiler (statistical mode) stuck at exit
mono-devel at assumetheposition.nl
Sat Jan 17 11:02:30 EST 2009
[This got previously sent from an unregistered e-mail address
accidentally, so if this mail is delivered twice I apologize]
With mono 2.2 I'm having pretty reproducable behavior where using the
statistical profiler hangs when my program is done. The stacktrace is:
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb7e4e5ae in pthread_join () from /lib/libpthread.so.0
#2 0xb7cea6fb in profiler_shutdown (prof=0x830a628) at
#3 0x08160b8e in mono_profiler_shutdown () at profiler.c:512
#4 0x0805b8e5 in mini_cleanup (domain=0x25ee0) at mini.c:14721
#5 0x080ef24c in mono_main (argc=4, argv=0xbf878da4) at driver.c:1667
#6 0x0805b071 in main (argc=Cannot access memory at address 0x0) at
A .mprof file is written, but it seems to be slightly corrupted, as I get:
ERROR: DecodingException in block of code 0, length 0, file offset
119376, block offset 0: unknown block code 0
(IProfilerEventHandler`8 handler) [0x00000]
Attempting to decode data printing block contents...
Current block of type 0 (file offset 119376, length 0)
While attempting decoding, got exception unknown block code 0
Stopping decoding after a DecodingException in block of code 0, length
0, file offset 119376, block offset 0: unknown block code 0
No allocations reported (on 1503 classes)
No execution time reported (on 1615 methods)
No jit time reported (on 1615 methods)
No statistical hits reported (on 1616 items)
when running mprog-decoder on it.
The program profiler is a command-line thingy and does not use threads.
Should I file a bug report in the tracker for this? I can provide the
executable if needed...
Platform: Gentoo Linux, kernel 2.6.26, glibc 2.6.1
More information about the Mono-devel-list