This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/12500] stabs debug info -- void no longer a predefined / builtin type
- From: "drow at mvista dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Oct 2003 17:13:47 -0000
- Subject: [Bug debug/12500] stabs debug info -- void no longer a predefined / builtin type
- References: <20031003154815.12500.taylor@candd.org>
- 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=12500
------- Additional Comments From drow at mvista dot com 2003-10-10 17:13 -------
Subject: Re: stabs debug info -- void no longer a predefined / builtin type
On Fri, Oct 10, 2003 at 04:59:06PM -0000, dtaylor at emc dot com wrote:
> I don't have one handy; but, with some hints / help, I'd be glad to.
>
> How does one write a gcc (not gdb!) testcase to test the debug information?
> Are there existing examples?
I don't need an automated testcase. I need something that will explain
the problem. I don't see the problem here so I need to understand why
you do.
The answer involves scan-assembly or something similar to that.
> The types printed in 2.95.3 permit you to generate correct debug
> information for things like:
>
> void *foo;
>
> Whereas I believe that the types printed in 3.3.1 -- wihich do not
> contain a void of any flavor -- do not permit such.
That's not correct since it worked in GDB. Which is where we usually
test such things. However, that was enough information to generate a
testcase; I believe your patch is right. Please send it to
gcc-patches.