[Mono-dev] Logging profiler (statistical mode) stuck at exit

[Alan McGovern]

Hi,

I reported the same issue yesterday to the developer in charge of the
logging profiler and it is actively being looked at. Hopefully it'll be
fixed soon. If you have issues in future, usually filing a bug on
http://bugzilla.novell.com would be the recommended thing to do.

Alan.

On Sat, Jan 17, 2009 at 4:02 PM, Paul Melis <mono-devel at assumetheposition.nl
> wrote:

> [This got previously sent from an unregistered e-mail address
> accidentally, so if this mail is delivered twice I apologize]
>
> Hi,
>
> With mono 2.2 I'm having pretty reproducable behavior where using the
> statistical profiler hangs when my program is done. The stacktrace is:
>
> (gdb) bt
> #0  0xffffe424 in __kernel_vsyscall ()
> #1  0xb7e4e5ae in pthread_join () from /lib/libpthread.so.0
> #2  0xb7cea6fb in profiler_shutdown (prof=0x830a628) at
> mono-profiler-logging.c:4726
> #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
> main.c:34
>
> 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
>  at
>
> Mono.Profiler.BlockData.Decode[LoadedClass,LoadedMethod,UnmanagedFunctionFromRegion,UnmanagedFunctionFromID,ExecutableMemoryRegion,LoadedElementHandler`7,HeapObject,HeapSnapshot]
> (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...
>
> Regards,
> Paul
>
> Platform: Gentoo Linux, kernel 2.6.26, glibc 2.6.1
>
>
>
>
>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20090117/e1ded87a/attachment.html