From: Tea <teawater@gmail.com>
To: "Michael Snyder" <msnyder@specifix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB record patch 0.1.3.1 for GDB-6.8 release
Date: Fri, 23 May 2008 14:33:00 -0000 [thread overview]
Message-ID: <daef60380805222004y48ecc2faw243a9f7a5c3d8401@mail.gmail.com> (raw)
In-Reply-To: <1211480158.3601.88.camel@localhost.localdomain>
Hi Michael,
How do you think about "query". I always forget the name of variable
that can set by user. So I more like query than it. :)
Thanks,
teawater
On Fri, May 23, 2008 at 2:15 AM, Michael Snyder <msnyder@specifix.com> wrote:
> On Fri, 2008-05-23 at 00:17 +0800, Tea wrote:
>> I think the good way is let user choice. When the user goes back a few
>> insns and he want to change the values of memory or register. The GDB
>> willtalk clear what will happen such as the future record will
>> destory, and ask user if he want to continue or not.
>> Then user can choice with himself.
>>
>> How do you think?
>
> I tend to agree about the user choice.
> Perhaps we could have it as a user-settable mode.
>
> Default might be "the past is read-only", ie. you
> can't change the state. But you could set a mode
> in which you can change the past (at the cost of
> destroying the future) -- and if you try to do it
> when the past is read-only, gdb could ask you if
> you want to change the mode.
>
> Is that clear? Or am I being too metaphorical?
>
> Michael
>
>
>
next prev parent reply other threads:[~2008-05-23 3:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 8:55 Tea
2008-05-20 4:33 ` Thiago Jung Bauermann
2008-05-20 6:38 ` Daniel Jacobowitz
2008-05-20 15:32 ` Tea
2008-05-20 18:51 ` Michael Snyder
2008-05-21 17:26 ` Tea
2008-05-20 15:33 ` Tea
2008-05-21 17:14 ` Tea
2008-05-21 22:01 ` Michael Snyder
2008-05-21 22:16 ` Thiago Jung Bauermann
2008-05-21 22:40 ` Daniel Jacobowitz
2008-05-22 15:08 ` Thiago Jung Bauermann
2008-05-23 2:54 ` Tea
2008-05-23 4:33 ` Michael Snyder
2008-05-23 14:33 ` Tea [this message]
2008-05-23 16:46 ` Michael Snyder
2008-05-23 18:16 ` Tea
2008-05-23 3:52 ` Pedro Alves
2008-05-23 14:31 ` Tea
2008-05-23 21:10 ` Pedro Alves
2008-06-08 6:53 ` teawater
2008-06-09 0:52 ` Pedro Alves
2008-06-09 3:00 ` Daniel Jacobowitz
2008-06-09 13:58 ` Thiago Jung Bauermann
2008-06-10 2:04 ` Michael Snyder
2008-06-09 22:56 ` Michael Snyder
2008-06-11 11:59 ` teawater
2008-06-11 20:03 ` Michael Snyder
2008-06-12 18:10 ` teawater
2008-06-13 6:08 ` Michael Snyder
2008-06-14 6:24 ` teawater
2008-06-14 10:31 ` Michael Snyder
2008-06-15 3:27 ` teawater
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=daef60380805222004y48ecc2faw243a9f7a5c3d8401@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@specifix.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