This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/862: regression: gdb.base/selftest.exp: "backtrace through signal handler"
- From: mec at shout dot net
- To: gdb-gnats at sources dot redhat dot com
- Date: 2 Dec 2002 23:45:20 -0000
- Subject: gdb/862: regression: gdb.base/selftest.exp: "backtrace through signal handler"
- Reply-to: mec at shout dot net
>Number: 862
>Category: gdb
>Synopsis: regression: gdb.base/selftest.exp: "backtrace through signal handler"
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Dec 02 15:48:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: mec@shout.net
>Release: gdb_5_3-branch%20021125, HEAD%20021125
>Organization:
>Environment:
target = native, host = i686-pc-linux-gnu%rh-8, gdb = HEAD%20021125, gcc = 3.2.1, binutils = 2.13.1, glibc = 2.2.93-5-rh, gformat = dwarf-2
>Description:
gdb.base/selftest.exp runs an inferior gdb. It sends a SIGINT to the inferior and then does a backtrace and expects to see certain stuff on the stack. In particular, it expects to see a function "main" in a file "*main.c".
As of 2002-09-26, function "main" moved from main.c to gdb.c, so the test pattern in selftest.exp is out of sync.
Amusingly, the test pattern also wants to see the string "read" somewhere in there. gdb doesn't call "read" on my host; it calls "poll". But there is a "readline" in the filenames on the stack so that part of the pattern matches by coincidence.
>How-To-Repeat:
Run selftest.exp on any gdb after 2002-09-26. The bug ought to be platform independent. It doesn't rely on signal handler semantics; it relies on the function "main" living in a file named "*main.c".
>Fix:
Update the pattern in selftest.exp.
>Release-Note:
>Audit-Trail:
>Unformatted: