| Summary: | Muine (or mono) crashes randomly as if somebody `kill -9`ed it -- prints "Killed" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tim Macfarlane <timmacfarlane> |
| Component: | [OLD] GNOME | Assignee: | dotnet project <dotnet> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Tim Macfarlane
2005-03-01 12:47:36 UTC
I've noticed some threading issues with mono-1.0.6, can you get me a good backtrace when this crashes, and try also with mono-1.0.6-r4? Thanks. From Muine being completely unreliable (crashing within 20sec of launching), it is now totally reliable - i've been running it now for hours. I haven't tested this but my guess is that it tends to crash during the import of a music library (reading mp3/ogg/flac headers, downloading album art, or something else). Now that my music library has been imported, it's running fine. I'll try to erase Muine's knowledge of my music library and import it again and see what happens -- then I'll get you a stack trace... BTW, do you mean a .Net backtrace or a GDB backtrace? How does one get a .Net backtrace? --debug? This stack frame was with CFLAGS="" Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 229385 (LWP 9091)] 0x43f759ff in ?? () (gdb) bt #0 0x43f759ff in ?? () #1 0xbe9ff568 in ?? () #2 0x43f751d0 in ?? () #3 0x0808eee0 in ?? () #4 0x095c8120 in ?? () #5 0xbe9ff4f4 in ?? () #6 0x40d9dacb in pthread_mutex_unlock () from /lib/libpthread.so.0 #7 0x43f740e0 in ?? () #8 0x095c8120 in ?? () #9 0x095c53b8 in ?? () #10 0x40d9daf9 in pthread_mutex_unlock () from /lib/libpthread.so.0 #11 0x43f73ddc in ?? () #12 0x08668a20 in ?? () #13 0x082720f0 in ?? () #14 0x0966e720 in ?? () #15 0xbe9ff87c in ?? () #16 0x00000000 in ?? () #17 0x00000001 in ?? () #18 0x4373fa58 in ?? () #19 0x00000000 in ?? () #20 0xbe9ff87c in ?? () #21 0x436cb88e in ?? () #22 0x08668a20 in ?? () #23 0x082720f0 in ?? () #24 0x400775b4 in mono_jit_compile_method_with_opt (method=0x8668a20, opt=136782064) at mini.c:8086 Previous frame inner to this frame (corrupt stack?) this stack frame with CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" SIGSEGV #0 0x43b4d82f in ?? () #1 0xbe7ff598 in ?? () #2 0x40d75967 in pthread_mutex_lock () from /lib/libpthread.so.0 #3 0x4380f128 in ?? () #4 0x08c41360 in ?? () #5 0x0964e2a0 in ?? () #6 0x00000001 in ?? () #7 0x40efd590 in __after_morecore_hook () from /lib/libc.so.6 #8 0x40d78ac0 in __pthread_unlock () from /lib/libpthread.so.0 #9 0x4380f014 in ?? () #10 0x082d1ed0 in ?? () #11 0x082c1f18 in ?? () #12 0x435f92f8 in ?? () #13 0xbe7ff8ac in ?? () #14 0x00000000 in ?? () #15 0x00000001 in ?? () #16 0x437f49d0 in ?? () #17 0x00000000 in ?? () #18 0xbe7ff8ac in ?? () #19 0x435f93d6 in ?? () #20 0x082d1ed0 in ?? () #21 0x082c1f18 in ?? () #22 0x401d5df7 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0 #23 0x096810c8 in ?? () #24 0x082c1f18 in ?? () #25 0xbe7ff8dc in ?? () #26 0x40076446 in mono_jit_compile_method (method=0x0) at mini.c:8115 sorry, neither of them seem to be very useful. GDB complained of a corrupt stack. This is still with 1.0.6 (not r4) I'll check that next Can you please try adding "-g" to your CFLAGS, and set FEATURES="nostrip" and re-emerge mono? That may help us get more useful debugging info. Also any news on mono-1.0.5-r4 (or the new -r5 which is pretty much the same thing)? Thanks. Marking NEEDINFO, please feel free to re-open when you have a better stack trace or results of trying the now stable mono-1.0.5-r5. Thanks. |
