This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/339: reread.exp fails on x86-linux
- From: geoffk at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Cc: Jim Blandy <jimb at redhat dot com>
- Date: 4 Feb 2002 17:32:42 -0000
- Subject: gdb/339: reread.exp fails on x86-linux
- Reply-to: geoffk at redhat dot com
>Number: 339
>Category: gdb
>Synopsis: reread.exp fails on x86-linux
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Feb 04 10:58:05 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: geoffk@redhat.com
>Release: 2002-02-02-cvs
>Organization:
>Environment:
Red Hat Linux 7; current CVS binutils and GCC.
>Description:
FAIL: gdb.base/reread.exp: second pass: breakpoint foo in first file
fails because the file seems not to be re-read. The log
file contains:
(gdb) break foo
Note: breakpoint 1 also set at pc 0x80483b4.
Breakpoint 2 at 0x80483b4: file /maat/heart/tbox/objs-20020202T122355Z/share/gdb
-testsuite/gdb.base/reread1.c, line 13.
(gdb) FAIL: gdb.base/reread.exp: second pass: breakpoint foo in first file
The problem seems to have been introduced between
20020120T015433Z and 20020122T065808Z.
>How-To-Repeat:
make check
>Fix:
Perhaps the following patch is relevant:
2002-01-21 Jim Blandy <jimb@redhat.com>
* infcmd.c (run_command): Check that the `exec' target layer's BFD
is up-to-date before running the program, not just when a program
exits.
but I haven't tried backing it out to see if that fixes the problem.
>Release-Note:
>Audit-Trail:
>Unformatted: