public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at magfr dot user dot lysator dot liu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/27017] New: Debug information for static local class members are not emitted
Date: Tue, 04 Apr 2006 08:35:00 -0000 [thread overview]
Message-ID: <bug-27017-7796@http.gcc.gnu.org/bugzilla/> (raw)
Given this program, compiled with 'g++ -ggdb3 program.C' and then run under
gdb.
when I get to f(int)::s::g(int) then I can't examine any local variables nor
any arguments.
When I rerun the compiler using 'g++ -ggdb3 -S program.C' and examine the
generated assembler there are no references to neither argument2 nor variable2,
but the string argument1 do show up.
--
Summary: Debug information for static local class members are not
emitted
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: gcc at magfr dot user dot lysator dot liu dot se
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27017
next reply other threads:[~2006-04-04 8:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 8:35 gcc at magfr dot user dot lysator dot liu dot se [this message]
2006-04-04 8:36 ` [Bug c++/27017] " gcc at magfr dot user dot lysator dot liu dot se
2006-04-04 8:44 ` [Bug debug/27017] " pinskia at gcc dot gnu dot org
2006-04-04 8:52 ` [Bug debug/27017] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-06-04 18:24 ` mmitchel at gcc dot gnu dot org
2006-06-06 4:11 ` drow at gcc dot gnu dot org
2006-08-25 14:35 ` drow at gcc dot gnu dot org
2006-08-25 17:27 ` drow at gcc dot gnu dot org
2006-08-26 3:48 ` drow at gcc dot gnu dot org
2006-10-23 14:15 ` drow at gcc dot gnu dot org
2007-02-03 16:48 ` [Bug debug/27017] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org
2007-02-03 20:28 ` pinskia at gcc dot gnu dot org
2007-02-14 9:10 ` mmitchel at gcc dot gnu dot org
2007-12-16 23:18 ` steven at gcc dot gnu dot org
2008-07-04 20:24 ` [Bug debug/27017] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-11-13 12:13 ` jakub at gcc dot gnu dot org
2008-11-13 21:07 ` jakub at gcc dot gnu dot org
2008-11-13 21:12 ` [Bug debug/27017] [4.2/4.3 " jakub at gcc dot gnu dot org
2009-03-31 19:34 ` [Bug debug/27017] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:37 ` rguenth at gcc dot gnu dot org
2010-05-22 18:17 ` rguenth at gcc dot gnu dot org
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=bug-27017-7796@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).