This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: c++/1025: failures in gdb.c++/ovldbreak.exp


The following reply was made to PR c++/1025; it has been noted by GNATS.

From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: c++/1025: failures in gdb.c++/ovldbreak.exp
Date: Tue, 4 Feb 2003 14:04:32 -0600

 I see these with:
 
   target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0
   gdb => 5.3, gdb_5_3-branch%200300201, HEAD%20030201
   gcc => 2.95.3
   binutils => 2.13.2.1, HEAD%20030128, 2.13.90.0.2-2
   gformat => dwarf-2
   libc=2.2.93-rh-5
 
 The test script sets a breakpoint on a member function that has
 an arg shorter than an 'int'.  Then it runs to the breakpoint and
 checks the value of the arg.  gdb shows an incorrect value for
 the argument.
 
 This happened with gcc 2.95.3 -gdwarf-2.  It did not happen with
 gcc 2.95.3 -gstabs+, and it did not happen with any gcc v3.
 
 The bug is not related to name overloading: that is working fine.
 Also, my test program 'small.cc' has all unique names, and still
 exhibits the problem.
 
 I attached a directory with a small program 'small.cc', the generated
 assembly code, an executable program, and a typescript of a gdb session.
 
 I suspect that David Carlton is seeing bugs from old binutils,
 but that I am seeing a different bug.
 
 Michael C


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]