From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: [doc patch] gdb.1: Add -p PID
Date: Fri, 05 Apr 2013 18:13:00 -0000 [thread overview]
Message-ID: <20130405151828.GA24147@host2.jankratochvil.net> (raw)
In-Reply-To: <20130405150101.GA15883@host2.jankratochvil.net>
On Fri, 05 Apr 2013 17:01:01 +0200, Jan Kratochvil wrote:
> > > +Fortran support will be added when a GNU Fortran compiler is ready.
> >
> > This list of languages is outdated, right?
> +
> > > +@smallexample
> > > +gdb program 1234
> > > +@end smallexample
> >
> > Should we mention "gdb -p PID" as well?
>
> Yes but that is unrelated to this patch which does only the technical
> conversion. OK, going to post a second patch for these.
Here.
Thanks,
jan
gdb/doc/
2013-04-04 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (gdb man): Mention option -p. Include Fortran to
the list of supported languages.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 2f9c68a..08c708b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -41623,8 +41623,9 @@ gdb [@option{-help}] [@option{-nh}] [@option{-nx}] [@option{-q}]
[@option{-b}@w{ }@var{bps}]
[@option{-tty=}@var{dev}] [@option{-s} @var{symfile}]
[@option{-e}@w{ }@var{prog}] [@option{-se}@w{ }@var{prog}]
-[@option{-c}@w{ }@var{core}] [@option{-x}@w{ }@var{cmds}]
- [@option{-d}@w{ }@var{dir}] [@var{prog}|@var{core}|@var{procID}]
+[@option{-c}@w{ }@var{core}] [@option{-p}@w{ }@var{procID}]
+ [@option{-x}@w{ }@var{cmds}] [@option{-d}@w{ }@var{dir}]
+[@var{prog}|@var{prog} @var{procID}|@var{prog} @var{core}]
@c man end
@c man begin DESCRIPTION gdb
@@ -41650,8 +41651,8 @@ Change things in your program, so you can experiment with correcting the
effects of one bug and go on to learn about another.
@end itemize
-You can use @value{GDBN} to debug programs written in C, C@t{++}, and Modula-2.
-Fortran support will be added when a GNU Fortran compiler is ready.
+You can use @value{GDBN} to debug programs written in C, C@t{++}, Fortran and
+Modula-2.
@value{GDBN} is invoked with the shell command @code{gdb}. Once started, it reads
commands from the terminal until you tell it to exit with the @value{GDBN}
@@ -41677,11 +41678,13 @@ to debug a running process:
@smallexample
gdb program 1234
+gdb -p 1234
@end smallexample
@noindent
would attach @value{GDBN} to process @code{1234} (unless you also have a file
named @file{1234}; @value{GDBN} does check for a core file first).
+With option @option{-p} you can omit the @var{program} filename.
Here are some of the most frequently needed @value{GDBN} commands:
next prev parent reply other threads:[~2013-04-05 15:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 20:14 [patch+doc] New gdbinit.5 man page Jan Kratochvil
2013-02-12 16:11 ` Eli Zaretskii
2013-02-12 16:22 ` Jan Kratochvil
2013-02-12 21:20 ` Tom Tromey
2013-02-13 17:42 ` Eli Zaretskii
2013-02-19 16:28 ` Jan Kratochvil
2013-02-19 18:03 ` Eli Zaretskii
2013-02-20 8:44 ` Jan Kratochvil
2013-02-20 19:26 ` Eli Zaretskii
2013-04-04 22:09 ` [patchv2+doc] New gdbinit.5 man page + converted gdb.1+gdbserver.1 Jan Kratochvil
2013-04-05 11:47 ` Eli Zaretskii
2013-04-05 13:03 ` Jan Kratochvil
2013-04-05 13:03 ` Eli Zaretskii
2013-04-05 17:50 ` Jan Kratochvil
2013-04-05 16:33 ` Jan Kratochvil
2013-04-05 18:13 ` Jan Kratochvil [this message]
2013-04-05 18:40 ` [doc patch] gdb.1: Add -p PID Eli Zaretskii
2013-04-06 9:01 ` [commit] " Jan Kratochvil
2013-04-05 18:29 ` [patchv2+doc] New gdbinit.5 man page + converted gdb.1+gdbserver.1 Eli Zaretskii
2013-04-05 19:06 ` Jan Kratochvil
2013-04-05 19:43 ` Eli Zaretskii
2013-04-06 6:47 ` Jan Kratochvil
2013-04-06 6:54 ` Eli Zaretskii
2013-04-06 8:45 ` [commit] " Jan Kratochvil
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=20130405151828.GA24147@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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