Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Fix hw watchpoints in process record.
Date: Wed, 04 Nov 2009 17:51:00 -0000	[thread overview]
Message-ID: <4AF1BF11.9030400@vmware.com> (raw)
In-Reply-To: <daef60380911031900p49d02fbfj5d139cd82dfc2e7c@mail.gmail.com>

Hui Zhu wrote:
> Hi Michael,
> 
> I do some test with this patch.  But sometime hb didn't work in replay mode.
> For example:
> Temporary breakpoint 1, main () at 1.c:20
> 20             int     b = 0;
> (gdb) record
> (gdb) n
> During symbol reading, incomplete CFI data; unspecified registers
> (e.g., eax) at 0x80483be.
> 21             int     c = 1;
> (gdb) hb
> Hardware assisted breakpoint 2 at 0x80483c8: file 1.c, line 21.
> (gdb) c
> Continuing.
> a = 0 b = 0 c = 1
> a = 3
> a = 3 b = 3 c = 1
> a = 3 b = 3 c = 2
> a = 1 b = 3 c = 2
> The next instruction is syscall exit_group.  It will make the program
> exit.  Do you want to stop the program?([y] or n)
> Process record: inferior program stopped.
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0xb7fe3405 in __kernel_vsyscall ()
> (gdb) rc
> Continuing.
> 
> Breakpoint 2, main () at 1.c:21
> 21             int     c = 1;
> (gdb) info b
> Num     Type           Disp Enb Address    What
> 2       hw breakpoint  keep y   0x080483c8 in main at 1.c:21
>         breakpoint already hit 1 time
> (gdb) c
> Continuing.
> 
> No more reverse-execution history.
> 0xb7fe3405 in __kernel_vsyscall ()
> (gdb) rc
> Continuing.
> 
> Breakpoint 2, main () at 1.c:21
> 21             int     c = 1;
> 
> 
> Thanks,
> Hui
> 


Source code for your test case?


  reply	other threads:[~2009-11-04 17:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01  1:23 Michael Snyder
2009-11-04  3:01 ` Hui Zhu
2009-11-04 17:51   ` Michael Snyder [this message]
2009-11-05  1:41     ` Hui Zhu
2009-11-05 18:41   ` Michael Snyder
2009-11-05 19:09     ` Pedro Alves
2009-11-12  0:27       ` Pedro Alves
2009-11-20 18:11         ` Michael Snyder
2009-11-21  9:41           ` Hui Zhu
2009-11-21 12:05             ` Pedro Alves
2009-11-21 19:50             ` Michael Snyder
2009-11-22  2:11               ` Hui Zhu
2009-11-22 12:56                 ` Pedro Alves
2009-11-22 15:45                   ` Pedro Alves
2009-11-22 19:22                     ` Eli Zaretskii
2009-11-24  1:58                     ` Pedro Alves
2009-11-26  2:28                       ` Hui Zhu
2009-11-22 15:50                   ` Pedro Alves
2009-11-22 20:21                 ` Michael Snyder
2009-11-22 23:03                   ` Pedro Alves
2009-11-23  3:17                     ` Hui Zhu
2009-11-09  3:18     ` Hui Zhu
2009-11-09 21:20       ` Michael Snyder
2009-11-10  7:39         ` Hui Zhu
2009-11-09 17:48     ` Tom Tromey
2009-11-10 23:32       ` Michael Snyder
2009-11-11  8:49         ` Hui Zhu
2009-11-12  0:05           ` 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=4AF1BF11.9030400@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