Well, I am not a gdb expert, but it could be that gdb change its process name as the program being traced. In order to check this, check with command "fuser" if the logfile in /tmp is used by faxgetty process. And, with command "lsof -p2468", check if this process uses only faxgetty binary or even gdb binary.
Thanks, Giuseppe -- 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
