New failures: gdb.base/recurse.exp

New failures: gdb.base/recurse.exp

[Fernando Nasser]

It is just me that is seeing it?  I just did a cvs update and those
appeared.

Fernando


> FAIL: gdb.base/recurse.exp: continue to second instance watchpoint, first time> FAIL: gdb.base/recurse.exp: continue to recurse (a = 4)
> FAIL: gdb.base/recurse.exp: continue to recurse (a = 3)
> FAIL: gdb.base/recurse.exp: continue to recurse (a = 2)
> FAIL: gdb.base/recurse.exp: continue to recurse (a = 1)
> FAIL: gdb.base/recurse.exp: continue to second instance watchpoint, second time
> FAIL: gdb.base/recurse.exp: second instance watchpoint deleted when leaving scope
> FAIL: gdb.base/recurse.exp: continue to first instance watchpoint, second time> FAIL: gdb.base/recurse.exp: first instance watchpoint deleted when leaving scope: the program is no longer running

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

Re: New failures: gdb.base/recurse.exp

[Kevin Buettner]

On May 10,  1:40pm, Fernando Nasser wrote:

> It is just me that is seeing it?  I just did a cvs update and those
> appeared.
> 
> > FAIL: gdb.base/recurse.exp: continue to second instance watchpoint, first time> FAIL: gdb.base/recurse.exp: continue to recurse (a = 4)
> > FAIL: gdb.base/recurse.exp: continue to recurse (a = 3)
> > FAIL: gdb.base/recurse.exp: continue to recurse (a = 2)
> > FAIL: gdb.base/recurse.exp: continue to recurse (a = 1)
> > FAIL: gdb.base/recurse.exp: continue to second instance watchpoint, second time
> > FAIL: gdb.base/recurse.exp: second instance watchpoint deleted when leaving scope
> > FAIL: gdb.base/recurse.exp: continue to first instance watchpoint, second time> FAIL: gdb.base/recurse.exp: first instance watchpoint deleted when leaving scope: the program is no longer running

I've just submitted a patch to fix these regressions.  See:

    http://sources.redhat.com/ml/gdb-patches/2001-05/msg00204.html

Kevin

Re: New failures: gdb.base/recurse.exp

[Michael Elizabeth Chastain]

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