This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
build/1028: testsuite: deprecate gdb_suppress_entire_file
- From: mec at shout dot net
- To: gdb-gnats at sources dot redhat dot com
- Date: 4 Feb 2003 16:04:19 -0000
- Subject: build/1028: testsuite: deprecate gdb_suppress_entire_file
- Reply-to: mec at shout dot net
>Number: 1028
>Category: build
>Synopsis: testsuite: deprecate gdb_suppress_entire_file
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Tue Feb 04 16:08:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: mec@shout.net
>Release: gdb 5.3
>Organization:
>Environment:
>Description:
gdb_suppress_entire_file smashes all the results for the current file, which is okay. Then it corrupts results in other files, which is not okay.
gdb_suppress_entire_file is implemented with funky global state variables, too, which is awkward.
Just call 'perror' and 'continue' instead.
>How-To-Repeat:
>Fix:
gdb.*/*.exp can be fixed incrementally.
I am going to start with gdb.c++/anon-union.exp, which legitimately fails to compile (gcc gives an ICE on legal code, and I have reported the bug to gcc -- PR gcc/9039). We can see how that works before wholesale conversion.
>Release-Note:
>Audit-Trail:
>Unformatted: