From: David Carlton <carlton@kealia.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: java inferior function call support
Date: Tue, 23 Mar 2004 22:48:00 -0000 [thread overview]
Message-ID: <yf2oeqnmb7w.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <4060BBCA.3040205@redhat.com> (Jeff Johnston's message of "Tue, 23 Mar 2004 17:35:54 -0500")
On Tue, 23 Mar 2004 17:35:54 -0500, Jeff Johnston <jjohnstn@redhat.com> said:
> However, this problem (gcc bugzilla bug 6587) has been open since
> May of 2003. How long does gdb suggest end-users should wait to
> debug their code? :)
Beats me. I don't quite understand how gcj and its corporate
sponsor(s?) allocate their efforts, to be honest; if I were working on
gcj, I would have pushed hard for that bug to be fixed. I just wish
we weren't in a situation where gdb is requested to go out of its way
to support a broken compiler without a show of effort from people
working on the compiler side. :-(
> I am perfectly willing to put a FIXME statement that when gcc
> finally gets around to fixing this problem, the code can be dropped.
I can imagine a compromise like this might be the best idea. But I'd
be a lot happier with it if we knew when the problem would get fixed.
(E.g. 3.4.0 will have it, 3.5.0 won't.)
David Carlton
carlton@kealia.com
prev parent reply other threads:[~2004-03-23 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 19:03 Jeff Johnston
2004-03-23 19:10 ` Daniel Jacobowitz
2004-03-24 20:38 ` Tom Tromey
2004-03-24 21:33 ` Jim Blandy
[not found] ` <4060B653.2050400@redhat.com>
2004-03-25 0:18 ` Daniel Jacobowitz
2004-03-23 19:21 ` David Carlton
2004-03-23 22:35 ` Jeff Johnston
2004-03-23 22:48 ` David Carlton [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=yf2oeqnmb7w.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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