From: Michael Snyder <msnyder@vmware.com>
To: teawater <teawater@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [reverse RFA] Remove process record warning code
Date: Sat, 18 Oct 2008 01:58:00 -0000 [thread overview]
Message-ID: <48F941C2.1010200@vmware.com> (raw)
In-Reply-To: <daef60380810171834l7b856b00u50ecef9689e05aaa@mail.gmail.com>
I'm worried that the naive user might think that he can
extend a recording session across several runs.
Might seem counter-intuitive, but I think the SID reverse
execution implementation will allow you to do that. If you
run the inferior multiple times, you can actually "back up"
into a previous execution.
I know Process Record won't let you do that, I'm just
saying, a user's intuition is not necessarily the same
as yours or mine...
teawater wrote:
> I think user already know P record will stop when inferior exit. So...
>
> How do you think about it?
>
>
> On Sat, Oct 18, 2008 at 01:23, Michael Snyder <msnyder@vmware.com> wrote:
>> You don't think you need this special warning?
>>
>> teawater wrote:
>>> Hi Michael,
>>>
>>> 2008-10-17 Hui Zhu <teawater@gmail.com>
>>>
>>> * infcmd.c (kill_if_already_running): Remove process record
>>> warning code.
>>>
>>> Thanks,
>>> Hui
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> --- a/ChangeLog
>>> +++ b/ChangeLog
>>> @@ -1,3 +1,8 @@
>>> +2008-10-17 Hui Zhu <teawater@gmail.com>
>>> +
>>> + * infcmd.c (kill_if_already_running): Remove process record
>>> + warning code.
>>> +
>>> 2008-10-15 Hui Zhu <teawater@gmail.com>
>>> Change "record-auto-delete" to "record-stop-at-limit".
>>> --- a/infcmd.c
>>> +++ b/infcmd.c
>>> @@ -51,7 +51,6 @@
>>> #include "exceptions.h"
>>> #include "cli/cli-decode.h"
>>> #include "gdbthread.h"
>>> -#include "record.h"
>>> /* Functions exported for general use, in inferior.h: */
>>> @@ -427,12 +426,8 @@ kill_if_already_running (int from_tty)
>>> restart it. */
>>> target_require_runnable ();
>>> - if (from_tty)
>>> - if (!query (RECORD_IS_USED ?
>>> - "The program being debugged has been started
>>> already,\n\
>>> -and is running in record/replay mode. Do you want to abandon\n\
>>> -the recording and start the program from the beginning? " :
>>> - "The program being debugged has been started
>>> already.\n\
>>> + if (from_tty
>>> + && !query ("The program being debugged has been started
>>> already.\n\
>>> Start it from the beginning? "))
>>> error (_("Program not restarted."));
>>> target_kill ();
>>
next prev parent reply other threads:[~2008-10-18 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 7:57 teawater
2008-10-17 10:58 ` Eli Zaretskii
2008-10-17 15:01 ` teawater
2008-10-17 17:28 ` Michael Snyder
2008-10-18 1:35 ` teawater
2008-10-18 1:58 ` Michael Snyder [this message]
2008-10-18 2:20 ` 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=48F941C2.1010200@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--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