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
> 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?
oh, probably the latter.....
inside the function, the backtrace shows:
(gdb) bt
#0 factorial (value=1) at ../../../gdb-cvs/gdb/testsuite/gdb.base/run.c:77
#1 0x00010584 in main (argc=1, argv=0xbff00220, envp=0xbff00228)
at ../../../gdb-cvs/gdb/testsuite/gdb.base/run.c:57
but in the epilogue:
(gdb) bt
#0 0x00010624 in factorial (value=1)
at ../../../gdb-cvs/gdb/testsuite/gdb.base/run.c:82
#1 0x403a146c in __libc_start_main () from /lib/libc.so.6
#2 0x00010480 in _start () at ../sysdeps/hppa/elf/start.S:67
> If the former, then maybe your patch is correct. If the latter, it
> should probably be an XFAIL.
ok, i'll look into this some more.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/