Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Paul Mundt <lethal@ChaoticDreams.ORG>
Cc: gdb@sources.redhat.com
Subject: Re: Software watchpoint breakage on SuperH
Date: Sat, 08 Jun 2002 22:10:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020609080541.12685C-100000@is> (raw)
In-Reply-To: <20020606085149.A6117@ChaoticDreams.ORG>


On Thu, 6 Jun 2002, Paul Mundt wrote:

> Watchpoint 3 deleted because the program has left the block in
> which its expression is valid.
> printf (format=3D0x4005dc "%d\n") at printf.c:33
> 33      printf.c: No such file or directory.
> 	in printf.c
> (gdb) c
> Continuing.
> 10
> 
> Program exited normally.
> (gdb)=20
> 
> Everything looks fine up until the point it tries to do the printf().
> 
> Is there something that needs to be implemented per target to support softw=
> are
> watchpoints properly? If not, does anyone have any suggestions as to what
> could be going wrong in the above, and better yet, suggestions for possible
> fixes?

It's not necessarily a problem with watchpoint support.  It could be that 
GDB cannot reliably detect where the current value of PC belong, so it 
mistakenly reports it's inside printf while in fact it's after `main' 
returns.

Another possibility is that the code which determines the current stack 
frame is faulty (that's the code GDB runs to know whether the watchpoint 
is in scope).


      reply	other threads:[~2002-06-09  5:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06  8:51 Paul Mundt
2002-06-08 22:10 ` Eli Zaretskii [this message]

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=Pine.SUN.3.91.1020609080541.12685C-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=lethal@ChaoticDreams.ORG \
    /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