On Fri, 2008-10-17 at 16:52 -0400, Jonathan Gagnon wrote: > Hi, > > I need help investigating a crash that occurs with mono 2.0. I get a > segmentation fault and mono crashes. I tried to debug it with gdb, > but I'm unable to find at which line of code the crash occurred. > Here's the output I get from gdb when the crash occurs : > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 1481681808 (LWP 4260)] > 0x57800936 in ?? () > (gdb) where > #0 0x57800936 in ?? () > #1 0x00000000 in ?? ()
try "thread apply all backtrace" this will show the stacktrace from every threads. > > I also tried running valgrind on my process, but the application > doesn't crash when running with valgrind, probably because the timing > is changed. It could be unrelated to timing. Valgrind will "fix" some issues that would normally crash your application. In those case the valgrind logs will contain the information. > I run on a 2 cpus machine and my application has around 60 threads. > > Any idea what I could do to get more information about the crash? > > Thanks, > > Jonathan > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
