Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] relax test in gdb.base/commands.exp
Date: Sun, 28 Nov 2004 17:43:00 -0000	[thread overview]
Message-ID: <20041128174334.GB24639@nevyn.them.org> (raw)
In-Reply-To: <20041122232915.GG9148@tausq.org>

On Mon, Nov 22, 2004 at 03:29:15PM -0800, Randolph Chung wrote:
> The regexp below checked for a specific line number in the caller when
> the watchpoint goes out of scope. On a target that emulates watchpoints
> with single stepping i've seen that we get the "watchpoint deleted"
> message when we're in the epilogue of a function. in this case the
> current line number may still be in the called function. This patch
> relaxes the line number checking a bit so we allow both cases (but not
> any random line). Tested on hppa-linux. ok?

Why do we get it in the epilogue?  Is it because the debug information
claims the variable has gone out of scope, or is it because of
faulty unwind information for the epilogue causing GDB to think the
frame has changed?

I know that GCC's epilogue unwind info is broken for all targets
(except maybe ia64).

If the former, then maybe your patch is correct.  If the latter, it
should probably be an XFAIL.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-11-28 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 23:29 Randolph Chung
2004-11-28 17:43 ` Daniel Jacobowitz [this message]
2004-11-28 19:19   ` Randolph Chung
2004-12-01  8:07   ` Randolph Chung

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=20041128174334.GB24639@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=randolph@tausq.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