[Mono-dev] Post-mortem debugging

2011-12-27 Thread Bassam Tabbara
Hello, I'm debugging a core file with gdb and I'm not able to find mono managed symbols: (gdb) where #0 0x7f93c9096ed5 in raise () from /lib/libc.so.6 #1 0x7f93c90983f3 in abort () from /lib/libc.so.6 #2 0x004933d0 in mono_handle_native_sigsegv (signal=-907561328, ctx=value

Re: [Mono-dev] Post-mortem debugging

2011-12-27 Thread Zoltan Varga
Hi, It won't work. The information required to construct managed stack traces is contained in runtime data structures, and it is only available while the program is running. You can AOT your application, then you will have more usable stack traces. Zoltan On Tue, Dec 27, 2011

Re: [Mono-dev] Post-mortem debugging

2011-12-27 Thread Zoltan Varga
Hi, Also, if the problem is reproducible, then you can run mono with the MONO_DEBUG=suspend-on-sigsegv environment variable set, which will force the runtime to spin in the sigsegv signal handler, allowing you to attach to it with gdb. Zoltan On Tue, Dec 27, 2011 at 11:43