From: David Daney <ddaney@caviumnetworks.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Remote core file debugging
Date: Thu, 30 Apr 2009 19:11:00 -0000 [thread overview]
Message-ID: <49F9F712.8060801@caviumnetworks.com> (raw)
In-Reply-To: <83k552dkw3.fsf@gnu.org>
Eli Zaretskii wrote:
> Is gdbserver supposed to support remote post-mortem debugging using a
> core file on a remote machine?
>
> 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?
>
I must be missing something, but why can't you move the core file to the
debugging host and debug it there with gdb?
David Daney
next prev parent reply other threads:[~2009-04-30 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 19:08 Eli Zaretskii
2009-04-30 19:11 ` David Daney [this message]
2009-04-30 19:28 ` Eli Zaretskii
2009-04-30 19:40 ` Michael Snyder
2009-05-04 0:29 ` Hui Zhu
2009-04-30 19:26 ` Daniel Jacobowitz
2009-04-30 19:31 ` Eli Zaretskii
2009-04-30 21:45 ` Mark Kettenis
2009-05-01 8:06 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F9F712.8060801@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox