From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] New command 'gcore'
Date: Wed, 12 Dec 2001 15:29:00 -0000 [thread overview]
Message-ID: <20011212152813.J28715@dr-evil.shagadelic.org> (raw)
In-Reply-To: <5567-Thu13Dec2001010400+0200-eliz@is.elta.co.il>; from eliz@is.elta.co.il on Thu, Dec 13, 2001 at 01:04:00AM +0200
On Thu, Dec 13, 2001 at 01:04:00AM +0200, Eli Zaretskii wrote:
> > From: Michael Snyder <msnyder@cygnus.com>
> > Newsgroups: cygnus.patches.gdb
> > Date: Wed, 12 Dec 2001 14:01:04 -0800
> >
> > 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.
>
> Sounds great!
Yah, gcore is cool, but it generally requires support from the kernel
in one way or another:
* You need to know which chunks of the address space are
actually mapped, and the protection of those regions.
* You need to know if a given chunk of the address space
should be dumped, even if it is mapped (consider a
memory-mapped device where reads produce side-effects).
* You need to know how many LWPs there are, and need to
be able to iterate over them.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2001-12-12 23:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 14:17 Michael Snyder
2001-12-12 15:05 ` Eli Zaretskii
2001-12-12 15:29 ` Jason R Thorpe [this message]
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=20011212152813.J28715@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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