On 18.08.2011 21:42 CE(S)T, Miguel de Icaza wrote: > Switch to teh aborted thread, and get a managed stack trace. > > To get that stack trace, follow the instructions on how to get > mono_backtrace from:
Sorry, I'm a total gdb noob. I can use Visual Studio well, but this is the hard stuff... Anyway, here's my try: (...) > Program received signal SIGABRT, Aborted. > 0x00007ffff71e1a75 in raise () from /lib/libc.so.6 > (gdb) mono_backtrace 15 > > Program received signal SIGSEGV, Segmentation fault. > 0x000000000055b4f4 in ?? () > The program being debugged was signaled while in a function called from GDB. > GDB remains in the frame where the signal was received. > To change this behavior use "set unwindonsignal on". > Evaluation of the expression containing the function > (mono_pmip) will be abandoned. > When the function is done executing, GDB will silently stop. > (gdb) Doesn't look like what you expected though. -- Yves Goergen "LonelyPixel" <[email protected]> Visit my web laboratory at http://beta.unclassified.de _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
