Tried id-utils packeage on my Ubuntu Gutsy,
$ mkid -o ~/mkid.ID .
it crashed with core.
Segmentation fault (core dumped)
However , no core appeared in directory where it was started.
$ ls -la core
ls: core: No such file or directory
under ubuntu core placed in /var/crash/
$ ls -la /var/crash/
drwxrwxrwt 2 root root 4096 2008-03-26 22:16 .
drwxr-xr-x 16 root root 4096 2007-10-21 01:49 ..
-rw------- 1 root root 44165 2008-03-22 20:01 libxml-libxml-perl.0.crash
-rw------- 1 root root 43697 2008-03-22 20:01 libxml-sax-perl.0.crash
-rwxr-xr-x 1 root root 0 2008-03-26 22:07 .lock
-rw------- 1 rtg rtg 1348820 2008-03-26 22:07 _usr_bin_mkid.1000.crash
then tryied
~$ gdb /usr/bin/mkid /var/crash/_usr_bin_mkid.1000.crash
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
"/var/crash/_usr_bin_mkid.1000.crash" is not a core dump: File format not recognized
(gdb)
No way to debug packaged app's coredumps in ubuntu?
Not so, this is solution:
$ head -78 /var/crash/_usr_bin_mkid.1000.crash
....77 lines with output ...
CoreDump: base64
And this:
https://wiki.ubuntu.com/DebuggingProgramCrash
page given me info on installing symbols;
then:
rtg@kubic-roman:~$ apport-unpack /var/crash/_usr_bin_mkid.1000.crash ~/mkid_crash
rtg@kubic-roman:~$ ls -la /home/rtg/mkid_crash/
###### 10052
drwxr-xr-x 2 rtg rtg 4096 2008-03-26 23:08 .
drwxr-xr-x 89 rtg rtg 401408 2008-03-26 23:08 ..
-rw-r--r-- 1 rtg rtg 4 2008-03-26 23:08 Architecture
-rw-r--r-- 1 rtg rtg 9805824 2008-03-26 23:08 CoreDump
-rw-r--r-- 1 rtg rtg 1 2008-03-26 23:08 CrashCounter
-rw-r--r-- 1 rtg rtg 24 2008-03-26 23:08 Date
-rw-r--r-- 1 rtg rtg 11 2008-03-26 23:08 DistroRelease
-rw-r--r-- 1 rtg rtg 13 2008-03-26 23:08 ExecutablePath
-rw-r--r-- 1 rtg rtg 5 2008-03-26 23:08 NonfreeKernelModules
-rw-r--r-- 1 rtg rtg 5 2008-03-26 23:08 ProblemType
-rw-r--r-- 1 rtg rtg 27 2008-03-26 23:08 ProcCmdline
-rw-r--r-- 1 rtg rtg 5 2008-03-26 23:08 ProcCwd
-rw-r--r-- 1 rtg rtg 158 2008-03-26 23:08 ProcEnviron
-rw-r--r-- 1 rtg rtg 1985 2008-03-26 23:08 ProcMaps
-rw-r--r-- 1 rtg rtg 660 2008-03-26 23:08 ProcStatus
-rw-r--r-- 1 rtg rtg 2 2008-03-26 23:08 Signal
-rw-r--r-- 1 rtg rtg 86 2008-03-26 23:08 Uname
-rw-r--r-- 1 rtg rtg 86 2008-03-26 23:08 UserGroups
coredump produced thats way.
finaly:
~$ gdb /usr/bin/mkid /home/rtg/mkid_crash/CoreDump
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/tls/i686/cmov/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
(no debugging symbols found)
Core was generated by `mkid -o /home/rtg/mkid.ID .'.
Program terminated with signal 11, Segmentation fault.
#0 0x0804f3a2 in ?? ()
(gdb) trace
trace command requires an argument
(gdb) where
#0 0x0804f3a2 in ?? ()
#1 0x00000000 in ?? ()
Yupp, not a much info.
Thats way I downloaded and installed it from sources (tar.gz from launchpad + patch + configure + make way).
uppps... this version crashes without core, even in crash :(
Finally, still searching for a way to obtain cores that were crashed.
tryied to edit:etc/security/limits.conf
uncommented core word containing line and tried to relogin:
and go to gdb again.
In gdb opened file as above, and seen
(gdb) where
...
#28 0x0804f3a7 in prune_file_names (str=0x0, from_link=0x0) at walker.c:685
#29 0x0804f3a7 in prune_file_names (str=0x0, from_link=0x0) at walker.c:685
#30 0x0804f3a7 in prune_file_names (str=0x0, from_link=0x0) at walker.c:685
#31 0x0804f3a7 in prune_file_names (str=0x0, from_link=0x0) at walker.c:685
...
No comments:
Post a Comment