Yes indeed, you can use either the *-dbg or the *-dbgsym packages. But you will need -- at least, if the SIG is in Evolution itself -- the evolution-data-server debug packages.
The backtrace you provided does not show any Evolution functions in the offending thread, in fact, *no* debug data at all: (gdb) backtrace full #0 0xb72cf6ba in ?? () from /usr/lib/libcairo.so.2 No symbol table info available. #1 0x00110101 in ?? () No symbol table info available. #2 0x001c8c8d in ?? () No symbol table info available. #3 0xbfe3ffa0 in ?? () No symbol table info available. #4 0x00010000 in ?? () No symbol table info available. #5 0x087c6818 in ?? () No symbol table info available. #6 0xbfe401ac in ?? () No symbol table info available. #7 0xd279e8e4 in ?? () No symbol table info available. #8 0x00000022 in ?? () No symbol table info available. #9 0x00000000 in ?? () No symbol table info available. So, we need at least the Evolution debug packages -- and perhaps others, depending on what function caused the SIGFPE. -- Floating Point Exception when starting evolution https://bugs.launchpad.net/bugs/157959 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
