From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Chris Markle <cmarkle@sendmail.com>, gdb@sources.redhat.com
Subject: Re: gcore or generate-core-file command?
Date: Wed, 14 Jul 2004 23:01:00 -0000 [thread overview]
Message-ID: <40F5B514.8070906@redhat.com> (raw)
In-Reply-To: <40F58CEB.9080308@gnu.org>
Andrew Cagney wrote:
>> Hi - I am currently using some moldy oldy versions of gdb that do not
>> appear
>> to have a way to generate core files (yes I know I should upgrade). I get
>> the impression that newer gdb versions have a gcore (or
>> generate-core-file?)
>> command. Is this the case or is this somehow limited to Linux or some
>> subset
>> of platforms (my interest here is generating cores with gdb on Solaris).
>> I've looked in the gdb doc and can't find refs to this ability. Is this
>> possible? Which version of gdb did this shwo up in? Thx in advance. Chris
>
>
> The command "gcore" was added to GDB 5.2. You're right though, it isn't
> doesn't appear to be documented.
>
> Michael, was there any documentation for this command?
<scrounge scrounge>... Drat. We had a conversation on gdb-patches
in January 2002, about what section of the manual they could go into.
That sort of trailed off without resolution, and I forgot to persue it.
There is of course the built-in help.
Yes, it does work on Solaris, and Linux, and Unixware.
And apparently bsd, and S390 (who knew?)
Chris, this is what the built-in help says:
(gdb) help gcore
Save a core file with the current state of the debugged process.
Argument is optional filename. Default filename is 'core.<process_id>'.
next prev parent reply other threads:[~2004-07-14 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 7:08 Chris Markle
2004-07-14 19:48 ` Andrew Cagney
2004-07-14 23:01 ` Michael Snyder [this message]
2004-10-25 9:27 ` 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=40F5B514.8070906@redhat.com \
--to=msnyder@redhat.com \
--cc=cagney@gnu.org \
--cc=cmarkle@sendmail.com \
--cc=gdb@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