From: Daniel Jacobowitz <drow@false.org>
To: ligang@sunnorth.com.cn
Cc: gdb@sourceware.org
Subject: Re: mi-watch.exp fail, pls help
Date: Fri, 18 Jan 2008 15:20:00 -0000 [thread overview]
Message-ID: <20080118152023.GA21602@caradoc.them.org> (raw)
In-Reply-To: <OF28CFE143.BB25B0B1-ON482573D4.0016C99C-482573D4.00184ABA@sunnorth.com.cn>
On Fri, Jan 18, 2008 at 12:25:43PM +0800, ligang@sunnorth.com.cn wrote:
> After a watchpoint trap in my target, the PC points to the instruction
> after the one that caused the trap.
> But after stepping over the traped instruction(example store), my target
> increases PC to the next instruction, so,
> the source line will not be correct. It occurs at whatever
> HAVE_NONSTEPPABLE_WATCHPOINT or HAVE_CONTINUABLE_WATCHPOINT.
If you have continuable watchpoints, GDB should not step after
hitting a watchpoint. The store has already happened when the
watchpoint triggers, right?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-18 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 3:58 ligang
2008-01-17 14:44 ` Daniel Jacobowitz
2008-01-18 4:26 ` ligang
2008-01-18 15:20 ` Daniel Jacobowitz [this message]
2008-01-21 1:16 ` ligang
2008-01-21 3:16 ` Daniel Jacobowitz
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=20080118152023.GA21602@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ligang@sunnorth.com.cn \
/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