public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/29044] Libiberty demangler can not handle new Java mangling.
Date: Wed, 13 Sep 2006 12:31:00 -0000 [thread overview]
Message-ID: <20060913123141.31151.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29044-3264@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2006-09-13 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 21:33 [Bug java/29044] New: " drow at gcc dot gnu dot org
2006-09-12 21:43 ` [Bug java/29044] " drow at gcc dot gnu dot org
2006-09-13 4:03 ` pinskia at gcc dot gnu dot org
2006-09-13 6:36 ` ian at airs dot com
2006-09-13 6:39 ` pinskia at gcc dot gnu dot org
2006-09-13 7:23 ` ian at airs dot com
2006-09-13 9:01 ` aph at gcc dot gnu dot org
2006-09-13 12:31 ` drow at gcc dot gnu dot org [this message]
2006-09-13 12:31 ` drow 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=20060913123141.31151.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).