From: Carlo Wood <carlo@alinoe.com>
To: gdb@sources.redhat.com
Subject: Re: gdb bugs showing while working on libcwd
Date: Tue, 28 May 2002 15:54:00 -0000 [thread overview]
Message-ID: <20020529005426.A9248@alinoe.com> (raw)
In-Reply-To: <20020528173746.GA13975@branoic.them.org>; from drow@mvista.com on Tue, May 28, 2002 at 01:37:46PM -0400
On Tue, May 28, 2002 at 01:37:46PM -0400, Daniel Jacobowitz wrote:
> I was just hoping someone more familiar than I with the mangling scheme
> could look at the existing one and figure out where the shortcoming
> is...
The problem is probably a design issue and it will be
a lot easier to just completely replace the demangler
with mine. Fixing the existing demangler is not a matter
of changing a few lines.
I've been asked before to donate my demangler to gdb,
someone translated it to C and then lost the code again
(I wrote it in C++). I've also been asked to donate
the demangler to libiberty (by the libstdc++/g++ people)
but there where some legal issues... its stupid, the FSF
makes it some times impossible to donate code it seems
(at least in my case). If one has to sign something
before they want to use code then what is the GPL
license good for? What about all those people
who use the GPL but never bother to gather signatures
from all over the world? The "problem" is that
Carlo Wood is not my real name, and although I am
willing to sign anything and donate anything under the
GPL, I do NOT want my real name somewhere on the web
or in a searchable database. Now EVERYTIME (and this
has come up at least three times very very seriously
in the past 8 years) I make a lot of effort to get
things arranged, people fail on me and nothing happens.
This time I am AGAIN waiting already several months
for the response of someone (I just want an 'ok, we
won't publish your real name)... Blah. No code then.
But in the meantime *I*'d like a working demangler
in libiberty as well actually, grrrmmbl.
Annoyed,
--
Carlo Wood <carlo@alinoe.com>
prev parent reply other threads:[~2002-05-28 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020522115242.C28512@redhat.com>
[not found] ` <20020523153816.A4454@alinoe.com>
[not found] ` <20020523094527.B25730@redhat.com>
2002-05-23 17:35 ` Carlo Wood
2002-05-23 18:58 ` Daniel Jacobowitz
2002-05-24 8:41 ` Huge problems with debugging threaded C++ programs Liam Stewart
2002-05-24 9:42 ` gdb bugs showing while working on libcwd Carlo Wood
2002-05-24 18:33 ` Carlo Wood
2002-05-24 18:41 ` Daniel Jacobowitz
2002-05-26 18:43 ` Carlo Wood
2002-05-26 23:03 ` Daniel Jacobowitz
2002-05-27 5:42 ` Carlo Wood
2002-05-27 11:05 ` Daniel Jacobowitz
2002-05-27 17:01 ` Carlo Wood
2002-05-28 1:17 ` Daniel Jacobowitz
2002-05-28 5:50 ` Carlo Wood
2002-05-28 10:37 ` Daniel Jacobowitz
2002-05-28 15:54 ` Carlo Wood [this message]
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=20020529005426.A9248@alinoe.com \
--to=carlo@alinoe.com \
--cc=gdb@sources.redhat.com \
/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