This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch] relax test in gdb.base/commands.exp
- From: Daniel Jacobowitz <drow at false dot org>
- To: Randolph Chung <randolph at tausq dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sun, 28 Nov 2004 12:43:34 -0500
- Subject: Re: [patch] relax test in gdb.base/commands.exp
- References: <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