public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "drow at false dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/1427] gcj should generate N_MAIN stab or DW_AT_entry_point dwarf2 debug info
Date: Mon, 08 Aug 2005 15:48:00 -0000 [thread overview]
Message-ID: <20050808154839.6329.qmail@sourceware.org> (raw)
In-Reply-To: <20001220121944.1427.tromey@gcc.gnu.org>
------- Additional Comments From drow at false dot org 2005-08-08 15:48 -------
Subject: Re: gcj should generate N_MAIN stab or DW_AT_entry_point dwarf2 debug info
On Mon, Aug 08, 2005 at 03:23:22PM -0000, aph at gcc dot gnu dot org wrote:
> I think we have deadlock here! It's easy enough to fix this once the changes
> have been made to gdb but pretty pointless otherwise.
I don't think there's any deadlock: it's easy to fix either without the
other, just no one's had time or interest to fix either.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1427
next prev parent reply other threads:[~2005-08-08 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001220121944.1427.tromey@gcc.gnu.org>
2005-08-08 11:28 ` aph at gcc dot gnu dot org
2005-08-08 15:19 ` green at redhat dot com
2005-08-08 15:24 ` aph at gcc dot gnu dot org
2005-08-08 15:45 ` pinskia at gcc dot gnu dot org
2005-08-08 15:48 ` drow at false dot org [this message]
2005-08-09 4:11 ` woodzltc at sources dot redhat dot com
2005-08-09 4:18 ` dberlin at dberlin dot org
2005-08-09 7:04 ` woodzltc at sources dot redhat dot com
2005-08-24 6:06 ` woodzltc at sources dot redhat dot com
[not found] <bug-1427-360@http.gcc.gnu.org/bugzilla/>
2005-11-15 3:04 ` woodzltc at sources dot redhat dot com
2006-10-14 14:17 ` steven 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=20050808154839.6329.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).