I managed to catch a backtrace of the segmentation fault, but I don't have debug symbols for dbus, and there doesn't appear to be a dbus-dbg package (?). The beginning of the trace looks like this:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7d18940 (LWP 5620)] 0xb7d8ed2a in strcmp () from /lib/tls/i686/cmov/libc.so.6 (gdb) backtrace full #0 0xb7d8ed2a in strcmp () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #1 0xb7f2dbfd in ?? () from /usr/bin/dbus-daemon No symbol table info available. Does anybody know a way to get the function name without a debug-symbol package? On Thu, Jun 5, 2008 at 12:39 PM, Carl Caum <[EMAIL PROTECTED]> wrote: > I'm experiencing the same problem. It's on an eight core server with 16 > Gigs of ram. It has two NICs that are bonded with mode 4. ACPI is > disabled and there is not a sound card. We have an average of 60 users > logged in to the system simultaneously through an NX session. At least > once a day, the DBUS daemon crashes causing numerous issues for NX > sessions. I can't find a cause. Is there any way to increase the log > level of dbus? Since it's random I can't monitor it effectively to see > what happens before it crashes. > > -- > dbus segmentation fault in hardy > https://bugs.launchpad.net/bugs/237527 > You received this bug notification because you are a direct subscriber > of the bug. > -- dbus segmentation fault in hardy https://bugs.launchpad.net/bugs/237527 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
