From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: pedro@codesourcery.com, mark.kettenis@xs4all.nl,
brobecker@adacore.com, gdb-patches@sourceware.org,
emachado@linux.vnet.ibm.com
Subject: Re: [patch] Forbid run with a core file loaded
Date: Thu, 08 Jul 2010 18:28:00 -0000 [thread overview]
Message-ID: <83eifd7rv9.fsf@gnu.org> (raw)
In-Reply-To: <20100708171648.GA29048@host0.dyn.jankratochvil.net>
> Date: Thu, 8 Jul 2010 19:16:48 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, mark.kettenis@xs4all.nl,
> brobecker@adacore.com, gdb-patches@sourceware.org,
> Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
>
> gdb/doc/
> 2010-07-08 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Make core files the process_stratum.
> * gdb.texinfo (Active Targets): Remove core_stratum. Include
> record_stratum example.
This part is okay, but please fix the punctuation as shown below:
There are multiple classes of targets such, as: processes, executable files or
recording sessions. Core files belong to the process class, making core file
and process mutually exclusive. Otherwise, @value{GDBN} can work concurrently
on multiple active targets, one in each class. This allows you to (for
example) start a process and inspect its activity, while still having access to
the executable file after the process finishes. Or if you start process
recording (@pxref{Reverse Execution}) and @code{reverse-step} there, you are
presented a virtual layer of the recording target, while the process target
remains stopped at the chronologically last point of the process execution.
Thanks.
next prev parent reply other threads:[~2010-07-08 18:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:47 Jan Kratochvil
2010-05-21 15:02 ` Mark Kettenis
2010-05-21 15:05 ` Pedro Alves
2010-05-21 15:54 ` Mark Kettenis
2010-05-21 16:08 ` Pedro Alves
2010-05-21 15:05 ` Joel Brobecker
2010-05-21 15:40 ` Mark Kettenis
2010-05-23 19:38 ` Jan Kratochvil
2010-05-23 21:08 ` Eli Zaretskii
2010-06-06 19:51 ` Jan Kratochvil
2010-06-06 23:08 ` Eli Zaretskii
2010-06-07 11:21 ` Pedro Alves
2010-06-08 2:33 ` Tom Tromey
2010-06-08 11:03 ` Pedro Alves
2010-07-08 17:17 ` Jan Kratochvil
2010-07-08 18:28 ` Eli Zaretskii [this message]
2010-07-19 18:02 ` Jan Kratochvil
2010-07-19 18:05 ` Eli Zaretskii
2010-07-19 18:16 ` Jan Kratochvil
2010-07-27 16:00 ` Joel Brobecker
2010-07-19 14:37 ` Pedro Alves
2010-05-23 21:16 ` Pedro Alves
2010-05-21 15:07 ` Jan Kratochvil
2010-05-21 15:04 ` Joel Brobecker
2010-05-21 15:06 ` Pedro Alves
2010-05-21 15:15 ` Joel Brobecker
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=83eifd7rv9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).