[Mono-dev] Post-mortem debugging

Bassam Tabbara bassam at symform.com
Tue Dec 27 16:54:24 EST 2011


I'm debugging a core file with gdb and I'm not able to find mono managed symbols:

(gdb) where
#0  0x00007f93c9096ed5 in raise () from /lib/libc.so.6
#1  0x00007f93c90983f3 in abort () from /lib/libc.so.6
#2  0x00000000004933d0 in mono_handle_native_sigsegv (signal=-907561328, ctx=<value optimized out>) at mini-exceptions.c:2246
#3  0x00000000004e6c9d in mono_arch_handle_altstack_exception (sigctx=0x7f93c9e7bc40, fault_addr=<value optimized out>, stack_ovf=0) at exceptions-amd64.c:957
#4  0x00000000004176e4 in mono_sigsegv_signal_handler (_dummy=11, info=0x7f93c9e7bd70, context=0x7f93c9e7bc40) at mini.c:5882
#5  <signal handler called>
#6  0x00007f93c9d18cc0 in ?? ()
#7  0x00000000413fb199 in ?? ()
#8  0x0000000000000025 in ?? ()
#9  0x00007f93c9cb6a90 in ?? ()
#10 0x00007f93c3cff150 in ?? ()
#11 0x0000000000000000 in ?? ()

(gdb) p mono_pmip(0x00007f93c9d18cc0)
You can't do that without a process to debug.

I looked at http://www.mono-project.com/Debugging and I can't tell if this is supposed to work on core dumps or not. How do you guys do it? What's your secret?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20111227/87b7857d/attachment.html 

More information about the Mono-devel-list mailing list