This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/12066] g++ generates stabs for "char *" that gdb cannot read
- From: "cgf at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Sep 2003 15:44:52 -0000
- Subject: [Bug debug/12066] g++ generates stabs for "char *" that gdb cannot read
- References: <20030826143029.12066.mec@shout.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
------- Additional Comments From cgf at redhat dot com 2003-09-17 15:44 -------
Subject: Re: g++ generates stabs for "char *" that gdb cannot read
On Mon, Sep 15, 2003 at 12:13:18AM -0000, mmitchel at gcc dot gnu dot org wrote:
>PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
>
>http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
>
>------- Additional Comments From mmitchel at gcc dot gnu dot org 2003-09-15 00:13 -------
>No, we certainly do not want to add back pushdecl.
>
>Instead, the stabs backend should generate stabs for the builtin types
>automatically, either as needed or always, at the start of the translation unit.
>
>I haven't had a chance to look at how to do that yet, but if it's getting in the
>way for the GDB folks, I will bump this up on my internal priority list.
This is definitely impacting my ability to use the gcc trunk with
cygwin. Code generation seems to be ok but I can't debug anything due
to this problem.