public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neroden at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/1907] symbol demangling by Throwable.printStackTrace
Date: Mon, 05 Jan 2004 06:30:00 -0000	[thread overview]
Message-ID: <20040105063038.16101.qmail@sources.redhat.com> (raw)
In-Reply-To: <20010207214600.1907.bothner@bothner.com>


------- Additional Comments From neroden at gcc dot gnu dot org  2004-01-05 06:30 -------
How about having libgcj depend on the demangler in libiberty directly?  This 
eliminates the need to invoke c++filt.  cp-demangle.c appears to be licensed 
appropriately (GPL + exception).  Is that a reasonable way to go? 
 
For addr2line, I see that it is GPL-licensed.  Hmm. 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1907


  parent reply	other threads:[~2004-01-05  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010207214600.1907.bothner@bothner.com>
2003-06-13 15:10 ` neroden@gcc.gnu.org
2003-11-11 14:57 ` aph at gcc dot gnu dot org
2004-01-05  6:30 ` neroden at gcc dot gnu dot org [this message]
2004-01-05 21:34 ` tromey at gcc dot gnu dot org
     [not found] <bug-1907-3679@http.gcc.gnu.org/bugzilla/>
2006-07-06 22:56 ` mckinlay at redhat dot com
2003-05-23 19:23 neroden@gcc.gnu.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=20040105063038.16101.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).