From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC] New command 'gcore'
Date: Wed, 12 Dec 2001 14:17:00 -0000 [thread overview]
Message-ID: <3C17D3A0.DE140BFB@cygnus.com> (raw)
I would like to discuss adding a new command 'gcore' to gdb.
This is at a very early stage, I just want to sound people out
about it.
The idea is that 'gcore' would cause gdb to generate a core image
of the inferior program (just like the 'gcore' unix command).
The user could drop a core file at any point in the inferior's
execution, and save the memory and register state for debugging later.
We ought to be able to cook up an elf core file pretty easily using
bfd.
This would probably require one or more new target and/or architecture
vectors, for instance to get a list of memory regions in use (which
would be easy for a /proc target, but might be progressively harder
for ptrace, sim, remote...). Some targets may not be able to
implement it right away, but in principle it could even be made
to work for remote embedded targets.
The holy grail, of course, would be to then give gdb the ability
to restart the process from the core file state. That would
give us a checkpoint-and-restart capability that very few
debuggers have ever had. But that's down the line...
next reply other threads:[~2001-12-12 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 14:17 Michael Snyder [this message]
2001-12-12 15:05 ` Eli Zaretskii
2001-12-12 15:29 ` Jason R Thorpe
2001-12-12 17:17 ` Andrew Cagney
2001-12-12 17:35 ` Jason R Thorpe
2001-12-12 17:48 ` Andrew Cagney
2001-12-12 18:06 ` Jason R Thorpe
2001-12-13 10:50 ` Andrew Cagney
2001-12-12 15:35 ` Kevin Buettner
2001-12-13 11:17 ` Michael Snyder
2001-12-26 12:32 ` Michael Snyder
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=3C17D3A0.DE140BFB@cygnus.com \
--to=msnyder@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/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