Bug 8912 - Crash is C++ demangling of code generated with gcc 2.95.3
Summary: Crash is C++ demangling of code generated with gcc 2.95.3
Status: RESOLVED OBSOLETE
Alias: None
Product: gdb
Classification: Unclassified
Component: c++ (show other bugs)
Version: 6.2
: P1 critical
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-08 22:28 UTC by craig.jeffree
Modified: 2022-12-23 19:21 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description craig.jeffree 2004-11-08 22:28:01 UTC
[Converted from Gnats 1807]

GDB crashes regularly while debugging code compiled with gcc 2.95.3

See more details in this thread:
http://sources.redhat.com/ml/gdb/2004-09/msg00057.html

and in the stack trace below:

> (gdb) bt
> #0  0xb74b0e7a in strcmp () from /lib/tls/libc.so.6
> #1  0x0814d00f in cp_print_class_method (
>     valaddr=0x15a88b68 "\030\214W\bnline/taam/src/m!", 
> type=0x15ab6c48,
>     stream=0x8283740) at cp-valprint.c:134
> #2  0x0814ca69 in c_val_print (type=0x11361658,
>     valaddr=0x15b2d3f8 "??4\bodel/dynamicX", embedded_offset=0,
>     address=139955224, stream=0x8283740, format=0, deref_ref=1,
> recurse=0,
>     pretty=Val_prettyprint) at c-valprint.c:449
> #3  0x080dbc40 in val_print (type=0x11361658,
>     valaddr=0x15b2d3f8 "??4\bodel/dynamicX", embedded_offset=0,
>     address=139955224, stream=0x8283740, format=0, deref_ref=1,
> recurse=0,
>     pretty=Val_pretty_default) at ./valprint.c:149

Release:
GDB 6.0, 6.1, 6.2

Environment:
Red Hat Enterprise Linux 3.0, gcc 2.95.3, ddd 3.3.1

How-To-Repeat:
Compile c++ code with gcc 2.95.3 and debug using GDB 6.x.  The problem occurs with or without DDD, however when DDD is driving GDB the crash will occur very frequently.
Comment 1 Tom Tromey 2022-12-23 19:21:24 UTC
Nobody ever looked into this when it was filed, but I think
it's safe to say this must have been fixed in the intervening years.
We debug gdb with itself all the time, and now that it's written
in C++, I feel we'd notice crashes like this.
Please reopen if you can still reproduce.