This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/33155] _stdcall assembler names in win32 vs gdb
- From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Apr 2008 07:23:53 -0000
- Subject: [Bug debug/33155] _stdcall assembler names in win32 vs gdb
- References: <bug-33155-4066@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from dannysmith at users dot sourceforge dot net 2008-04-26 07:23 -------
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > What is the status on this? Does reverting the langhooks.c change remanifest
> > > PR27067?
> > >
> > No. PR27067 is fixed by
> > cp/mangle.c (mangle_decl): Call targetm.mangle_decl_assembler_name.
>
> I see; then should the langhooks.c bit be reverted to fix this bug, or do you
> think it will be able to be solved soon some other way?
>
I don't know how to solve it. I thought it might be a GDB bug concerning
DW_AT_MIPS_linkage_name and an assumption by GDB that "C" assembler names are
not mangled, but I haven't had time to follow up. But on windows, the external
DECL_ASSEMBLER_NAME for stdcall symbols look mangled to me, in C as well as
C++, and gcc/dwarf2out.c:add_name_and_src_coords_attributes() does the right
thing.
But ,as I said, I haven't had time to study GDB.
Danny
I
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33155