Bug 55099 - gdb + g++3
Summary: gdb + g++3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gdb
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-25 15:33 UTC by Neal D. Becker
Modified: 2007-04-18 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-11-29 00:11:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Neal D. Becker 2001-10-25 15:33:01 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901

Description of problem:
gdb can't grok vector<complex<double>> compiled by g++3

(gdb) p roots[0]
$8 = (Complex &) @0x80504f8: {_M_value = Invalid C/C++ type code 20 in
symbol table.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.compile with g++3 -g
2.
3.
	

Additional info:

Comment 1 Trond Eivind Glomsrxd 2001-10-26 16:36:43 UTC
Example file?

Comment 2 Bill Nottingham 2001-10-29 19:12:17 UTC
Also, does it work if you have gcc output dwarf2 debug info?

Comment 3 Neal D. Becker 2001-10-30 21:08:13 UTC
#include <complex>

int main () {
  typedef std::complex<double> Complex;
  Complex x (1.,0.);
}

g++3 -o Test Test.cc

gdb Test
b main
runp x
$1 = {_M_value = Invalid C/C++ type code 20 in symbol table

Comment 4 Neal D. Becker 2001-10-30 21:12:09 UTC
No difference if I do -ggdb.

Comment 5 Trond Eivind Glomsrxd 2001-10-30 21:26:37 UTC
"-gdwarf-2" doesn't help, and it's still a problem on the latest CVS snapshots
of gdb.

Comment 6 Trond Eivind Glomsrxd 2001-11-29 00:11:14 UTC
Still a problem with gdb 5.1


Comment 7 Trond Eivind Glomsrxd 2002-03-20 19:39:02 UTC
Fixed in gdb-5.1.90CVS-2 (it prints out a warning about not handling 16byte
floating point numbers, but at least tries to print the numbers...)


Note You need to log in before you can comment on or make changes to this bug.