From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Pedro Alves <pedro@codesourcery.com>,
teawater <teawater@gmail.com>
Subject: Re: [RFA] Reverse Debugging, 1/5
Date: Wed, 08 Oct 2008 00:32:00 -0000 [thread overview]
Message-ID: <48EBFEE7.6020500@vmware.com> (raw)
In-Reply-To: <20081008001541.GA3810@adacore.com>
Joel Brobecker wrote:
>>> My own view was a little simpler: Delete the target_set_execdir method,
>> I'm guessing you meant "get" here?
>
> Ooops! yes, that' right.
>
>>> and replace all the calls with a reference to the infrun global. I would
>>> keep the target_set_execdir more or less as is; otherwise, you'll need
>>> some kind of observer to notice when the execdir changes. The
>>> "to_can_go_backwards" is an interesting idea, but in my opinion only
>>> makes sense if the target_set_execdir method is removed. Otherwise,
>>> we can treat target_set_execdir == NULL as cannot-go-backwards.
>> OK, so you're saying that "target_set_execdir" will set the
>> global infrun variable, not a target-defined variable?
>
> Not quite, actually. Roughly, when the user changes the exec direction,
> we call target_set_execdir and, if the call succeeded, then update the
> direction known in infrun. Or perhaps you or others have better ideas?
Just, well, then target_set_execdir does not actually
set the exec direction -- instead it sort of tells you
if it's *ok* to set the exec direction -- which is what
I would think of as target_can_reverse.
I'm putting this together, and will have a new patch submission shortly.
next prev parent reply other threads:[~2008-10-08 0:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 19:18 Michael Snyder
2008-10-03 19:04 ` Doug Evans
2008-10-03 20:44 ` Michael Snyder
2008-10-06 20:30 ` Joel Brobecker
2008-10-06 21:03 ` Michael Snyder
2008-10-06 21:12 ` Daniel Jacobowitz
2008-10-06 21:20 ` Michael Snyder
2008-10-06 21:25 ` Daniel Jacobowitz
2008-10-06 21:46 ` Michael Snyder
2008-10-06 22:23 ` Joel Brobecker
2008-10-07 0:45 ` Michael Snyder
2008-10-07 3:49 ` Joel Brobecker
2008-10-07 18:30 ` Michael Snyder
2008-10-08 0:16 ` Joel Brobecker
2008-10-08 0:32 ` Michael Snyder [this message]
2008-10-08 0:55 ` Joel Brobecker
2008-10-08 1:46 ` Michael Snyder
2008-10-08 2:59 ` Joel Brobecker
2008-10-07 5:02 ` Daniel Jacobowitz
2008-10-06 21:45 ` Pedro Alves
2008-10-06 22:14 ` Michael Snyder
2008-10-06 22:35 ` Pedro Alves
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=48EBFEE7.6020500@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=teawater@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