(1) Pedro: running evolution now does not generate a new crash file in /var/crash (which
may be a separate bug). The old crash from a day ago or so does not contain debug
symbols. Do I have to invoke /usr/bin/evolution with a wrapper script or something
to get it to generate a /var/crash log?
(2) David: I installed evolution-dbg, however the stack from 'gdb /usr/bin/evolution' still has no useful
symbols. The evolution-dbg package contains this file
/usr/lib/debug/usr/bin/evolution
that appears like it may be a debug version
of evolution, but gdb on this still does not produce any useful info:
fcdevldev01:/var/crash> ls -l /usr/lib/debug/usr/bin/evolution
-rw-r--r-- 1 root root 402499 2008-02-25 19:16 /usr/lib/debug/usr/bin/evolution
fcdevldev01:/var/crash> file !$
file /usr/lib/debug/usr/bin/evolution
/usr/lib/debug/usr/bin/evolution: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
gdb /usr/lib/debug/usr/bin/evolution
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) r
Starting program: /usr/lib/debug/usr/bin/evolution
/usr/lib/debug/usr/bin/evolution: Permission denied.
Program exited with code 01.
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
You can't do that without a process to debug.
(gdb) bt
No stack.
(gdb)
---
(3) Given (1) and (2), I am stuck without any obvious way to generate a meaningful
crash, and for some reason the /var/crash generator is not generating crash
logs for evolution. Any advice is greatly appreciated!
(1) Pedro: running evolution now does not generate a new crash file in /var/crash (which
may be a separate bug). The old crash from a day ago or so does not contain debug
symbols. Do I have to invoke /usr/bin/evolution with a wrapper script or something
to get it to generate a /var/crash log?
(2) David: I installed evolution-dbg, however the stack from 'gdb /usr/bin/evolution' still has no useful debug/usr/ bin/evolution
symbols. The evolution-dbg package contains this file
/usr/lib/
that appears like it may be a debug version
of evolution, but gdb on this still does not produce any useful info:
fcdevldev01: /var/crash> ls -l /usr/lib/ debug/usr/ bin/evolution debug/usr/ bin/evolution /var/crash> file !$ debug/usr/ bin/evolution debug/usr/ bin/evolution: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
-rw-r--r-- 1 root root 402499 2008-02-25 19:16 /usr/lib/
fcdevldev01:
file /usr/lib/
/usr/lib/
gdb /usr/lib/ debug/usr/ bin/evolution gnu.org/ licenses/ gpl.html> i686/cmov/ libthread_ db.so.1" . debug/usr/ bin/evolution debug/usr/ bin/evolution: Permission denied.
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/
(gdb) r
Starting program: /usr/lib/
/usr/lib/
Program exited with code 01.
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
You can't do that without a process to debug.
(gdb) bt
No stack.
(gdb)
---
(3) Given (1) and (2), I am stuck without any obvious way to generate a meaningful
crash, and for some reason the /var/crash generator is not generating crash
logs for evolution. Any advice is greatly appreciated!