From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add new cmd line parameter "--pid" for attach.
Date: Mon, 07 Jan 2002 11:07:00 -0000 [thread overview]
Message-ID: <3C39F0DA.762692AF@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020107111652.9979A-100000@is>
Eli Zaretskii wrote:
>
> On Sun, 6 Jan 2002, Michael Snyder wrote:
>
> > Eli Zaretskii wrote:
> > >
> > > > Date: Sat, 05 Jan 2002 13:07:42 -0800
> > > > From: Michael Snyder <msnyder@redhat.com>
> > > >
> > > > + @item -pid @ver{number}
> > > > + @itemx -p @var{number}
> > > > + @cindex @code{--pid}
> > > > + @cindex @code{-p}
> > > > + Use @var{number} as a process ID to attach to.
> > > > +
> > > > + @item -p @var{number}
> > > > + Connect to process ID @var{number}, as with the @code{attach} command.
> > > > + If there is no such process, @value{GDBN} will attempt to open a core
> > > > + file named @var{number}.
> > >
> > > This seems to describe the new option twice. You probably meant to
> > > merge the two description parts, and eliminate the second "@item -p".
> >
> > Actually, I just copied what was there already for the --core option.
>
> I'm not sure what you mean. I looked in gdb.texinfo, and all I see for
> "--core" there is this:
>
> @item -core @var{file}
> @itemx -c @var{file}
> @cindex @code{--core}
> @cindex @code{-c}
> Use file @var{file} as a core dump to examine.
>
> This doesn't describe --core twice, and doesn't use @item -c twice.
Look at the next lines after that.
next prev parent reply other threads:[~2002-01-07 19:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 19:25 Michael Snyder
2002-01-05 0:59 ` Eli Zaretskii
2002-01-05 13:12 ` Michael Snyder
2002-01-06 0:04 ` Eli Zaretskii
2002-01-06 21:26 ` Michael Snyder
2002-01-07 1:20 ` Eli Zaretskii
2002-01-07 11:07 ` Michael Snyder [this message]
2002-01-07 12:28 ` Eli Zaretskii
2002-01-07 13:39 ` Michael Snyder
2002-01-07 16:14 ` Michael Snyder
2002-01-08 0:53 ` Eli Zaretskii
2002-01-08 15:15 ` Michael Snyder
2002-01-07 18:55 ` Elena Zannoni
2002-01-08 15:15 ` Michael Snyder
2002-01-08 16:59 ` Andrew Cagney
2002-01-10 13:09 ` Elena Zannoni
2002-01-10 16:20 ` Andrew Cagney
2002-01-10 16:46 ` Elena Zannoni
2002-01-11 2:19 ` Richard Earnshaw
2002-01-10 17:06 ` Michael Snyder
2002-01-10 17:28 ` Andrew Cagney
2002-01-10 17:56 ` Frank Ch. Eigler
2002-01-11 12:26 ` Michael Snyder
2002-01-10 23:53 ` Eli Zaretskii
2002-01-10 13:13 ` Elena Zannoni
2002-01-10 14:49 ` Michael Snyder
2002-01-10 15:02 ` Michael Snyder
2002-01-10 23:23 ` Eli Zaretskii
2002-01-11 12:24 ` 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=3C39F0DA.762692AF@redhat.com \
--to=msnyder@redhat.com \
--cc=eliz@is.elta.co.il \
--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