Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	 	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] let record_resume fail immediately on error
Date: Wed, 09 Sep 2009 02:05:00 -0000	[thread overview]
Message-ID: <daef60380909081905j6ee3c0b0tc8a938b99fc5a4e9@mail.gmail.com> (raw)
In-Reply-To: <4AA68C92.7070905@vmware.com>

[-- Attachment #1: Type: text/plain, Size: 3882 bytes --]

On Wed, Sep 9, 2009 at 00:55, Michael Snyder<msnyder@vmware.com> wrote:
> Hui Zhu wrote:
>>
>> On Tue, Sep 8, 2009 at 15:25, Hui Zhu<teawater@gmail.com> wrote:
>>>
>>> If GDB call error in record_resume, user cannot keep debug the inferior.
>>>
>>> Hui
>>>
>>> On Tue, Sep 8, 2009 at 15:23, Hui Zhu<teawater@gmail.com> wrote:
>>>>
>>>> The "record_resume_error" in gdb-cvs is to make user after get a error
>>>> of record_message, they can "record stop" close the record and keep
>>>> debug the inferior.
>>>>
>>>> Thanks,
>>>> Hui
>>>>
>>>> On Tue, Sep 8, 2009 at 14:58, Joel Brobecker<brobecker@adacore.com>
>>>> wrote:
>>>>>>
>>>>>>   if (!RECORD_IS_REPLAY)
>>>>>>     {
>>>>>>       if (do_record_message (get_current_regcache ()))
>>>>>> -        {
>>>>>> -          record_resume_error = 0;
>>>>>> -        }
>>>>>> -      else
>>>>>> -        {
>>>>>> -          record_resume_error = 1;
>>>>>> -          return;
>>>>>> -        }
>>>>>> +     internal_error (__FILE__, __LINE__,
>>>>>> +                     _("record_resume: do_record_message failed."));
>>>>>> +
>>>>>
>>>>> Forgive me if I'm wrong, as I don't know the record.c code at all, but
>>>>> I cannot help but think that the internal_error is suspicious here.
>>>>> Why is this an internal_error?
>>>>>
>>>>> --
>>>>> Joel
>>>>>
>>
>> Hi guys,
>>
>> I make a patch that make "record_resume_error" work better.  I did
>> some test.  It seems better than before.
>
> Could you explain what you mean by better?
> I mean, what behavior are you looking for here?
>
> Here is the behavior that I see --- I am making a recording,
> I say "continue", and after a while this "record_resume_error"
> is triggered, and gdb stops and says "No more reverse-execution history."
>
> I would never expect to see that message during recording.

In before, GDB cannot throw error in record_resume (It just in my
memory, maybe I am wrong).
If we try to do it, it will get:
(gdb) c
Continuing.
Cannot execute this command while the selected thread is running.
So I add record_resume_error to let record_wait to handle it.

But record_wait cannot call error too.  So I let it:
	  /* If record_resume get error, return directly.  */
	  status->kind = TARGET_WAITKIND_STOPPED;
	  status->value.sig = TARGET_SIGNAL_0;
	  return inferior_ptid;

But I found that record_resume can call error now.  So I make a new
patch for it.

Could you help me try it?


Thanks,
Hui

2009-09-09  Hui Zhu  <teawater@gmail.com>

	* record.c (record_resume_error): Deleted.
	(record_resume): Call record_message.
	(record_wait): Deleted record_resume_error.

---
 record.c |   19 +------------------
 1 file changed, 1 insertion(+), 18 deletions(-)

--- a/record.c
+++ b/record.c
@@ -516,7 +516,6 @@ record_close (int quitting)
 }

 static int record_resume_step = 0;
-static int record_resume_error;

 static void
 record_resume (struct target_ops *ops, ptid_t ptid, int step,
@@ -526,15 +525,7 @@ record_resume (struct target_ops *ops, p

   if (!RECORD_IS_REPLAY)
     {
-      if (do_record_message (get_current_regcache ()))
-        {
-          record_resume_error = 0;
-        }
-      else
-        {
-          record_resume_error = 1;
-          return;
-        }
+      record_message (get_current_regcache ());
       record_beneath_to_resume (record_beneath_to_resume_ops, ptid, 1,
                                 siggnal);
     }
@@ -586,14 +577,6 @@ record_wait (struct target_ops *ops,

   if (!RECORD_IS_REPLAY)
     {
-      if (record_resume_error)
-	{
-	  /* If record_resume get error, return directly.  */
-	  status->kind = TARGET_WAITKIND_STOPPED;
-	  status->value.sig = TARGET_SIGNAL_ABRT;
-	  return inferior_ptid;
-	}
-
       if (record_resume_step)
 	{
 	  /* This is a single step.  */

[-- Attachment #2: prec-fix-error-handler.txt --]
[-- Type: text/plain, Size: 1166 bytes --]

---
 record.c |   19 +------------------
 1 file changed, 1 insertion(+), 18 deletions(-)

--- a/record.c
+++ b/record.c
@@ -516,7 +516,6 @@ record_close (int quitting)
 }
 
 static int record_resume_step = 0;
-static int record_resume_error;
 
 static void
 record_resume (struct target_ops *ops, ptid_t ptid, int step,
@@ -526,15 +525,7 @@ record_resume (struct target_ops *ops, p
 
   if (!RECORD_IS_REPLAY)
     {
-      if (do_record_message (get_current_regcache ()))
-        {
-          record_resume_error = 0;
-        }
-      else
-        {
-          record_resume_error = 1;
-          return;
-        }
+      record_message (get_current_regcache ());
       record_beneath_to_resume (record_beneath_to_resume_ops, ptid, 1,
                                 siggnal);
     }
@@ -586,14 +577,6 @@ record_wait (struct target_ops *ops,
 
   if (!RECORD_IS_REPLAY)
     {
-      if (record_resume_error)
-	{
-	  /* If record_resume get error, return directly.  */
-	  status->kind = TARGET_WAITKIND_STOPPED;
-	  status->value.sig = TARGET_SIGNAL_ABRT;
-	  return inferior_ptid;
-	}
-
       if (record_resume_step)
 	{
 	  /* This is a single step.  */

  reply	other threads:[~2009-09-09  2:05 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08  4:03 Michael Snyder
2009-09-08  5:00 ` Hui Zhu
2009-09-08  6:59 ` Joel Brobecker
2009-09-08  7:23   ` Hui Zhu
2009-09-08  7:25     ` Hui Zhu
2009-09-08  7:53       ` Hui Zhu
2009-09-08 16:57         ` Michael Snyder
2009-09-09  2:05           ` Hui Zhu [this message]
2009-09-12  2:40             ` Hui Zhu
2009-09-24  3:10             ` Hui Zhu
2009-09-26 18:35               ` Michael Snyder
2009-09-27  2:51                 ` Hui Zhu
2009-09-28  9:27                 ` Hui Zhu
2009-09-28 18:12                   ` Joel Brobecker
2009-09-29  2:33                     ` Hui Zhu
2009-09-29 21:29                       ` Joel Brobecker
2009-09-29 23:57                         ` Hui Zhu
2009-10-14  2:10                           ` Joel Brobecker
2009-10-14  2:28                             ` Hui Zhu
2009-10-14  2:42                               ` Joel Brobecker
2009-10-15  4:38                                 ` Hui Zhu
2009-10-15  4:58                                   ` Joel Brobecker
2009-10-15  7:17                                     ` Hui Zhu
2009-10-15 16:23                                       ` Joel Brobecker
2009-10-15 17:18                                         ` Michael Snyder
2009-10-16  3:37                                           ` Hui Zhu
2009-10-20  3:17                                             ` Hui Zhu
2009-10-23  7:29                                               ` Hui Zhu
2009-11-03  2:17                                                 ` Hui Zhu
2009-11-03 18:57                                                   ` Michael Snyder
2009-11-04  5:15                                                     ` Hui Zhu
2009-11-10  7:02                                                       ` Hui Zhu
2009-11-10 22:05                                                         ` Tom Tromey
2009-11-11  0:55                                                           ` Hui Zhu
2009-11-24  6:16                                                             ` Hui Zhu
2009-11-24 17:14                                                               ` Tom Tromey
2009-11-25  2:00                                                                 ` Hui Zhu
2009-11-25 16:25                                                                   ` Joel Brobecker
2009-11-25 17:59                                                                     ` Tom Tromey
2009-11-26  6:40                                                                       ` Hui Zhu
2009-11-28  0:29                                                                         ` Hui Zhu
2009-12-01 22:27                                                                         ` Tom Tromey
2009-12-02  3:23                                                                           ` Hui Zhu
2009-12-07 15:01                                                                             ` Hui Zhu
2009-12-12  8:41                                                                             ` Hui Zhu
2009-12-21 20:45                                                                               ` Tom Tromey
2009-12-22  3:18                                                                                 ` Hui Zhu
2009-09-08 16:54       ` Michael Snyder
2009-09-08 16:52     ` Michael Snyder
2009-09-08 16:50   ` Michael Snyder
2009-09-08 17:05     ` Joel Brobecker

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=daef60380909081905j6ee3c0b0tc8a938b99fc5a4e9@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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