From: Michael Snyder <msnyder@specifix.com>
To: Roberto Saltini <house.83@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Breakpoints saving
Date: Mon, 31 Mar 2008 23:01:00 -0000 [thread overview]
Message-ID: <1206985149.31772.39.camel@localhost.localdomain> (raw)
In-Reply-To: <53d46f3a0803302230r9b8f28dsacafd52c23d27d4e@mail.gmail.com>
On Mon, 2008-03-31 at 07:30 +0200, Roberto Saltini wrote:
> Hello,
> is it possible to save somewhere the actual configuration of a debug
> session(breakpoints, wathcpoints, displays) ? Or directly in the target file?
> Thank you.
Not really. It is a request that we've seen before.
Problem is that a lot of that info is very context
sensative, so it's not really the case that you can,
for instance, save it in the middle of a session and
then reload it at the beginning of another session.
As a work around, you can save the outputs of eg.
"info break" and use those to reconstruct your
session state by hand later.
prev parent reply other threads:[~2008-03-31 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53d46f3a0803301930x73d080dfv4de7c78dc6d4312f@mail.gmail.com>
2008-03-31 12:52 ` Roberto Saltini
2008-03-31 23:01 ` Michael Snyder [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=1206985149.31772.39.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sourceware.org \
--cc=house.83@gmail.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