This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: New failures: gdb.base/recurse.exp
- To: fnasser at redhat dot com, gdb at sources dot redhat dot com
- Subject: Re: New failures: gdb.base/recurse.exp
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Thu, 10 May 2001 11:07:22 -0700
I saw some of those on a branch inside Red Hat a few weeks ago.
Let me cut-and-paste some verbiage:
This test script sets a watchpoint on a local variable in a recursive
function. It then observes the watchpoint as the function recurses
and returns.
In the configurations that FAIL, gdb deletes the watchpoint when
the function calls itself. gdb says that "the program has left the
block in which its expression is valid". This is an error in gdb.
When gdb deletes the watchpoint, it stops and prints a message on
the current line (the open brace of the function being called).
This message desynchronizes the test script and causes a cascade
of FAILs.
All of the configurations which fail use software watchpoints.
Software watchpoints use watchpoint_check, which calls
find_frame_addr_in_frame_chain to find this information.
Michael