This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Forbid run with a core file loaded
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: pedro at codesourcery dot com, mark dot kettenis at xs4all dot nl, brobecker at adacore dot com, gdb-patches at sourceware dot org, emachado at linux dot vnet dot ibm dot com
- Date: Thu, 08 Jul 2010 21:25:46 +0300
- Subject: Re: [patch] Forbid run with a core file loaded
- References: <20100606195033.GA9710@host0.dyn.jankratochvil.net> <201006071220.58289.pedro@codesourcery.com> <20100708171648.GA29048@host0.dyn.jankratochvil.net>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.