Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: ligang@sunnorth.com.cn
Cc: gdb@sourceware.org
Subject: Re: mi-watch.exp fail, pls help
Date: Thu, 17 Jan 2008 14:44:00 -0000	[thread overview]
Message-ID: <20080117144410.GF9907@caradoc.them.org> (raw)
In-Reply-To: <OF32C474D6.F65DFBB4-ON482573D3.0014F615-482573D3.0015C0CE@sunnorth.com.cn>

On Thu, Jan 17, 2008 at 11:57:33AM +0800, ligang@sunnorth.com.cn wrote:
> After setting watchpoint to C, it will be hit at 0x11e, and PC will be 
> 0x120 at the time,
> but GDB will execute a single step, after that, PC will be 0x122, so 
> source line will be 36 but not 
> expected 35.
> Anyone can tell me how to resolve this problem?

Check your target configuration.  GDB thinks you have non-steppable
watchpoints, but you actually have continuable watchpoints.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-01-17 14:44 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 [this message]
2008-01-18  4:26   ` ligang
2008-01-18 15:20     ` Daniel Jacobowitz
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=20080117144410.GF9907@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