This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
c++/1025: failures in gdb.c++/ovldbreak.exp
- From: carlton at math dot stanford dot edu
- To: gdb-gnats at sources dot redhat dot com
- Date: 4 Feb 2003 00:50:03 -0000
- Subject: c++/1025: failures in gdb.c++/ovldbreak.exp
- Reply-to: carlton at math dot stanford dot edu
>Number: 1025
>Category: c++
>Synopsis: failures in gdb.c++/ovldbreak.exp
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Feb 04 00:58:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: carlton@math.stanford.edu
>Release: GNU gdb 2002-12-23-cvs
>Organization:
>Environment:
i686-pc-linux-gnu, GCC 3.1, DWARF-2
>Description:
I consistently get the following test failures in gdb.c++/ovldbreak.exp:
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : char
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : signed char
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned char
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : short
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned short
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : double
In all cases, the wrong value is printed out for the arg
for the method call.
Strangely enough, Michael Chastain's tables never show
the last two failures, and only show the first 4 failures
with GCC 2.95.3/DWARF-2. Admittedly, he doesn't test
the GCC version that I use; I see them with 3.1 and with
3.2.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: