From: Paul Smith <paul@mad-scientist.net>
To: gdb@sourceware.org
Subject: gdbserver with a core file?
Date: Thu, 01 Mar 2018 13:04:00 -0000 [thread overview]
Message-ID: <1519909479.3684.41.camel@mad-scientist.net> (raw)
Has anyone every considered, or actually implemented, the ability to
use gdbserver to debug a core file remotely in addition to debugging
live processes?
More and more I'm seeing core files dumped on AWS or Google Cloud
instances. It's really expensive (and slow!!) to copy these many-GB
cores back to my local system for debugging, and they're often only
needed for an hour or so.
Of course I could debug them in the cloud, but either I need to go
without source code during debugging or I need to copy my source code
into the cloud, neither of which is particularly appealing for all
kinds of reasons.
When I was working on embedded systems gdbserver was a lifesaver, and
it would save me a lot of time (and $$) if I could debug core files
with it.
Any thoughts on this?
next reply other threads:[~2018-03-01 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 13:04 Paul Smith [this message]
2018-03-01 13:54 ` taylor, david
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=1519909479.3684.41.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--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