Giuseppe: I don't know if this is a problem or not.
I killed "faxgetty", then executed "gdb-wrapper.sh /usr/local/sbin/faxgetty -D ttyS0". Faxgetty once again appears in the process tree, but the log at /tmp/gdb-24080.log reads: <blank line> Program exited normally. No stack. /tmp/gdb-24080.batch:11: Error in sourced command file: No symbol table is loaded. Use the "file" command. The result of "file /usr/local/sbin/faxgetty" is: /usr/local/sbin/faxgetty: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped As I said earlier, I had compiled hylafax 6.05 from source, but did not use any switches for including debugging symbols. gdb does not appear in the process tree, nor does any process with a pid of 24080. (faxgetty's pid is 24086) The result of "fuser /tmp/gdb-24080.log" is: /tmp/gdb-24080.log: 24086 The result of "lsof -p24086" is: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME faxgetty 24086 uucp cwd DIR 8,3 4096 397885 /var/spool/hylafax faxgetty 24086 uucp rtd DIR 8,3 4096 2 / faxgetty 24086 uucp txt REG 8,3 477484 136322 /usr/local/sbin/faxgetty faxgetty 24086 uucp mem REG 8,3 113964 410036 /lib/ld-2.11.1.so faxgetty 24086 uucp mem REG 8,3 9748 410063 /lib/tls/i686/cmov/libutil-2.11.1.so faxgetty 24086 uucp mem REG 8,3 477612 136841 /usr/local/lib/libhylafax-6.0.so.5 faxgetty 24086 uucp mem REG 8,3 366580 145310 /usr/lib/libtiff.so.4.3.2 faxgetty 24086 uucp mem REG 8,3 79512 391113 /lib/libz.so.1.2.3.3 faxgetty 24086 uucp mem REG 8,3 975088 136780 /usr/lib/libstdc++.so.6.0.13 faxgetty 24086 uucp mem REG 8,3 149392 391032 /lib/tls/i686/cmov/libm-2.11.1.so faxgetty 24086 uucp mem REG 8,3 120368 390998 /lib/libgcc_s.so.1 faxgetty 24086 uucp mem REG 8,3 1405508 391024 /lib/tls/i686/cmov/libc-2.11.1.so faxgetty 24086 uucp mem REG 8,3 128616 136484 /usr/lib/libjpeg.so.62.0.0 faxgetty 24086 uucp mem REG 8,3 30496 391054 /lib/tls/i686/cmov/libnss_compat-2.11.1.so faxgetty 24086 uucp mem REG 8,3 79676 391042 /lib/tls/i686/cmov/libnsl-2.11.1.so faxgetty 24086 uucp mem REG 8,3 34408 391089 /lib/tls/i686/cmov/libnss_nis-2.11.1.so faxgetty 24086 uucp mem REG 8,3 42572 391076 /lib/tls/i686/cmov/libnss_files-2.11.1.so faxgetty 24086 uucp mem REG 8,3 256324 140902 /usr/lib/locale/en_US.utf8/LC_CTYPE faxgetty 24086 uucp mem REG 8,3 2454 207218 /usr/lib/locale/en_US.utf8/LC_TIME faxgetty 24086 uucp mem REG 8,3 26048 153218 /usr/lib/gconv/gconv-modules.cache faxgetty 24086 uucp 0u CHR 1,3 0t0 791 /dev/null faxgetty 24086 uucp 1u CHR 1,3 0t0 791 /dev/null faxgetty 24086 uucp 2u CHR 1,3 0t0 791 /dev/null faxgetty 24086 uucp 3r FIFO 0,8 0t0 524621 pipe faxgetty 24086 uucp 4w FIFO 0,8 0t0 524621 pipe faxgetty 24086 uucp 5r REG 8,3 270 269268 /tmp/gdb-24080.batch (deleted) faxgetty 24086 uucp 6w REG 8,3 144 276646 /tmp/gdb-24080.log faxgetty 24086 uucp 7w REG 8,3 17 398290 /var/spool/hylafax/status/ttyS0 faxgetty 24086 uucp 8u FIFO 8,3 0t0 398300 /var/spool/hylafax/FIFO.ttyS0 faxgetty 24086 uucp 9u CHR 1,3 0t0 791 /dev/null faxgetty 24086 uucp 10w FIFO 8,3 0t0 398284 /var/spool/hylafax/FIFO faxgetty 24086 uucp 11u unix 0xe364e3c0 0t0 524633 socket faxgetty 24086 uucp 12u CHR 4,64 0t0 969 /dev/ttyS0 >From this information, can you tell: is gdb "watching" faxgetty, ready to >produce useful information on the next segfault? Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
