This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Remote core file debugging
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: eliz at gnu dot org
- Cc: gdb at sourceware dot org
- Date: Thu, 30 Apr 2009 23:37:05 +0200 (CEST)
- Subject: Re: Remote core file debugging
- References: <83k552dkw3.fsf@gnu.org>
> Date: Thu, 30 Apr 2009 22:03:24 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> Is gdbserver supposed to support remote post-mortem debugging using a
> core file on a remote machine?
I don't think it is.
> I have a situation where producing a backtrace from a dead program's
> core file by running GDB on the machine where the application crashed
> is impractical. This is because the program has huge amounts of debug
> info, so starting GDB eats up all memory, which is a no-no, since the
> application which restarted itself after a crash must be up at all
> times, and eating up too much memory causes the OS to kill
> applications. So I'm looking for ways of producing the equivalent of
> "bt full", but without firing up GDB on the target system (a Red Hat
> box).
>
> If gdbserver does not support this, what alternatives do I have?
Copy the core file and binaries to a somewhat more powerful machine
and use a cross-gdb (the same you'd probably use with gdbserver)?