Hiho... Javier Fernández-Sanguino Peña schrieb: > Can you attach to the children cron process with gdb, run it and then > show me the output of running 'bt' from gdb?
Hm, that didn't help much...
Not only are there no debugging symbols in the cron child, but I
apparently triggered a bug in gdb, as well.
Take a look:
[EMAIL PROTECTED]:~# kill -STOP `pidof cron
[EMAIL PROTECTED]:~# gdb /usr/sbin/cron `pidof cron`
GNU gdb 6.3.90_20051119-debian
Copyright 2004 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/libthread_db.so.1".
Attaching to program: /usr/sbin/cron, process 4675
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
Reading symbols from /lib/libpam.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /lib/libselinux.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libselinux.so.1
Reading symbols from /lib/tls/libc.so.6...
(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/tls/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libdl.so.2
Reading symbols from /lib/ld-linux.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/tls/libnss_compat.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/tls/libnss_compat.so.2
Reading symbols from /lib/tls/libnsl.so.1...
(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libnsl.so.1
Reading symbols from /lib/tls/libnss_nis.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/tls/libnss_nis.so.2
Reading symbols from /lib/tls/libnss_files.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib/tls/libnss_files.so.2
0xb7ebd7ab in nanosleep ()
from /lib/tls/libc.so.6
(gdb) set follow-for- k child
(gdb) cont
Continuing.
Program received signal SIGSTOP, Stopped (signal).
0xb7ebd7ab in nanosleep () from /lib/tls/libc.so.6
(gdb) cont
Continuing.
Program received signal SIGSTOP, Stopped (signal).
0xb7ebd7ab in nanosleep () from /lib/tls/libc.so.6
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
[Switching to process 14631]
0x0804c27f in ?? ()
(gdb) bt full
#0 0x0804c27f in ?? ()
No symbol table info available.
#1 0x08057538 in ?? ()
No symbol table info available.
#2 0x08057558 in ?? ()
No symbol table info available.
#3 0xb7e268cc in ?? ()
No symbol table info available.
#4 0x08057630 in ?? ()
No symbol table info available.
#5 0x08057600 in ?? ()
No symbol table info available.
#6 0x00000000 in ?? ()
No symbol table info available.
(gdb) The program is running. Exit anyway? (y or n) n
Not confirmed.
(gdb) cont
Continuing.
/space/debian/gdb/build-area/gdb-6.3.90.20051119/gdb/linux-nat.c:544:
internal-error: unknown ptrace event 5
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
/space/debian/gdb/build-area/gdb-6.3.90.20051119/gdb/linux-nat.c:544:
internal-error: unknown ptrace event 5
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted
[EMAIL PROTECTED]:~#
--
Friedrich Delgado Friedrichs <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
