This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug java/29044] Libiberty demangler can not handle new Java mangling.
- From: "drow at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Sep 2006 12:31:41 -0000
- Subject: [Bug java/29044] Libiberty demangler can not handle new Java mangling.
- References: <bug-29044-3264@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from drow at gcc dot gnu dot org 2006-09-13 12:31 -------
Subject: Re: Libiberty demangler can not handle new Java mangling.
> I don't understand why this bug has been reported.
The bug was reported because the combination of the mangling change and
the demangler postfix behavior messes up GDB. You used to be able to
say "break 'jmain.main(java.lang.String[])'" but now that's not found;
you'd have to add the trailing void manually. As per your message:
http://gcc.gnu.org/ml/java-patches/2005-q3/msg00434.html
Several affected tests in the GDB testsuite broke. Of course they're
somewhat provisional tests because there are earlier tests in the same
file which use much more user-friendly forms, that are still not
supported by GDB. The Java debug support has not gotten much love
lately.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29044