Please describe the problem:
While reporting bug #375062 I found that bug-buddy does not handle gdb failures very well. This bug was a crash in a process (seahorse-daemon) with an executable file that was owned by root and setuid (to prevent an attacker from ptracing the daemon and retrieving the user's private keys).

When run from the console, gdb does write a 'permission denied' error to stderr. I think bug-buddy should try to capture errors such as these, and at least display them in the debug info text widget.

There is a problem in that that GDB does not correctly set its exit status:

 $ gdb -batch -p $(pgrep ssh-agent); echo $?
 ptrace: Operation not permitted.
 /home/sam/3737: No such file or directory.
 0

Perhaps it would be best to always include all output (both stdout and stderr) from GDB in bug reports.

Steps to reproduce:
On Linux, create a setuid process and crash it; bug-buddy will be unable to use gdb to attach to the process and the stack trace will be empty.

Actual results:


Expected results:


Does this happen every time?


Other information: