public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: Using reverse execution
Date: Fri, 16 Sep 2005 14:00:00 -0000	[thread overview]
Message-ID: <432ACFFB.9040204@apple.com> (raw)
In-Reply-To: <ull1xmgyd.fsf@gnu.org>

Eli Zaretskii wrote:

>
>Anyway, I really don't understand why we need to discuss all this at
>such length.  Either there is a volunteer who is ready to do the job
>of adding this, or there isn't.  In the latter case, there's no sense
>arguing about the value of the feature; in the former case, will we
>really consider rejecting the patches that implement the feature
>because some of us are unsure how useful it will be?
>
>
I must not be getting my point across very well then. Apple is quite
interested in getting reverse execution going outside of the simulator
context, and I've been playing with some prototype machinery. However,
it's clear that a full-blown handles-every-situation implementation
will require a huge amount of kernel hacking in addition to the GDB
part. I don't want to get into a situation like that of tracepoints,
where the feature ultimately falls by the wayside because it's too
narrow in applicability and implementation.

So I'm not questioning the value of the feature, but trying to get a
sense of the user requirements. Undoing a single a=b+c is relatively
easy, and my prototype can do that now, but reversing through 15
minutes of iTunes usage is fiendishly hard, and would require a major
commitment by Apple involving multiple software groups. The level of
effort I'll be able to get depends on what we think the requirements
look like.

This is a rare opportunity to weigh in on a feature *before* it's
implemented; an unfamiliar situation I know :-) , but something
people ought to take advantage of rather than brush off. A lot of
past GDB projects would have come out better had there been open
discussion earlier in the process.

Stan


  reply	other threads:[~2005-09-16 14:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  1:17 Stan Shebs
2005-09-13  3:43 ` Eli Zaretskii
2005-09-14  0:36   ` Stan Shebs
2005-09-14  3:42     ` Eli Zaretskii
2005-09-14 22:34       ` Stan Shebs
2005-09-15  3:37         ` Eli Zaretskii
2005-09-15  5:36           ` Stan Shebs
2005-09-15 15:14             ` Eli Zaretskii
2005-09-15 18:02               ` Jason Molenda
2005-09-15 20:12                 ` Stan Shebs
2005-09-16 10:42                   ` Eli Zaretskii
2005-09-16 14:00                     ` Stan Shebs [this message]
2005-09-16 16:22                       ` Eli Zaretskii
2005-09-16 18:03                         ` Stan Shebs
2005-09-16 20:50                           ` Eli Zaretskii
2005-09-23 23:20                             ` Stan Shebs
2005-09-16 17:50                       ` Ian Lance Taylor
2005-09-16 10:43                 ` Eli Zaretskii
2005-09-13 18:11 ` Min Xu (Hsu)
2005-09-13 22:01   ` Jim Blandy
2005-09-14  0:42     ` Stan Shebs
2005-09-16 12:03 ` Ramana Radhakrishnan
2005-09-20 22:47 Michael Snyder
2005-09-20 22:56 Michael Snyder
2005-09-20 23:14 ` Ian Lance Taylor
2005-09-21  3:40   ` Eli Zaretskii
2005-09-21  4:00     ` Ian Lance Taylor
2005-09-21 17:52       ` Eli Zaretskii
2005-09-21 20:37       ` Michael Snyder
2005-09-24  0:46         ` Stan Shebs
2005-09-24  1:10           ` Michael Snyder
2005-09-24 10:05           ` Eli Zaretskii
2005-09-27 22:00           ` Jim Blandy
2005-09-21  4:03     ` Daniel Jacobowitz
2005-09-21 16:56 ` Paul Gilliam
2005-09-23 23:44 ` Stan Shebs
2005-09-20 23:11 Michael Snyder
2005-09-24  0:07 ` Stan Shebs

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=432ACFFB.9040204@apple.com \
    --to=shebs@apple.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).