From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: Doco for "generate-core-file" -- where?
Date: Fri, 04 Jan 2002 23:51:00 -0000 [thread overview]
Message-ID: <4839-Sat05Jan2002094842+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3C3617F0.3020906@cygnus.com> (message from Andrew Cagney on Fri, 04 Jan 2002 16:00:32 -0500)
> Date: Fri, 04 Jan 2002 16:00:32 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> >
> > I was looking for a section involving files, but of course
> > gdb does not write very many files (mostly reads them).
>
> For what its worth, the save command (assuming it gets off the ground
> :-) will also need a home. It would make sense for that comand to also
> go in the same section as gcore.
Then perhaps make a new section about commands which read and write
auxiliary files, and put the docs of gcore there. The others will be
added as they are coded.
prev parent reply other threads:[~2002-01-05 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 18:28 Michael Snyder
2002-01-04 0:52 ` Eli Zaretskii
2002-01-04 12:25 ` Michael Snyder
2002-01-04 13:00 ` Andrew Cagney
2002-01-04 23:51 ` Eli Zaretskii [this message]
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=4839-Sat05Jan2002094842+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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