From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: [rfa/doco] PROBLEMS: add gdb/1516
Date: Tue, 27 Jan 2004 06:07:00 -0000 [thread overview]
Message-ID: <20040127060727.DF38A4B363@berman.michael-chastain.com> (raw)
This patch adds a description of gdb/1516 to the PROBLEMS file.
This is a regression with g++ 2.95.3 -gdwarf-2 and we've decided
not to fix it, so I want to document it.
By the way, this file needs (1) a copyright notice and (2) to be
updated from "gdb 6.0" to "gdb 6.1".
Leaving those issues aside -- okay to commit this?
Michael C
2004-01-27 Michael Chastain <mec.gnu@mindspring.com>
* PROBLEMS: add gdb/1516.
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.20
diff -c -3 -p -r1.20 PROBLEMS
*** PROBLEMS 24 Oct 2003 17:37:03 -0000 1.20
--- PROBLEMS 27 Jan 2004 06:04:45 -0000
*************** Fortunately the ARM target, in the GDB's
*** 23,28 ****
--- 23,40 ----
updated so people encountering problems should consider downloading a
more current GDB (http://www.gnu.org/software/gdb/current).
+ gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2
+
+ With gcc 2.95.3 and the dwarf-2 debugging format, classes which are
+ defined locally to a function include the demangled name of the function
+ as part of their name. For example, if a function "foobar" contains a
+ local class definition "Local", gdb will say that the name of the class
+ type is "foobar__Fi.0:Local".
+
+ This applies only to classes where the class type is defined inside a
+ function, not to variables defined with types that are defined somewhere
+ outside any function (which most types are).
+
gdb/1091: Constructor breakpoints ignored
gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
next reply other threads:[~2004-01-27 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 6:07 Michael Elizabeth Chastain [this message]
2004-01-27 9:30 ` Eli Zaretskii
2004-01-27 14:06 ` Andrew Cagney
2004-01-27 20:14 ` Eli Zaretskii
2004-01-27 10:44 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040127060727.DF38A4B363@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox