public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@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:20:00 -0000 [thread overview] Message-ID: <20050808151413.20652.qmail@sourceware.org> (raw) In-Reply-To: <20001220121944.1427.tromey@gcc.gnu.org> ------- Additional Comments From green at redhat dot com 2005-08-08 15:14 ------- (In reply to comment #9) > Anthony, do you think this bug should be fixed? Yes, I think so. > What is the status of your gdb > patch? It hasn't been applied. I never followed up on the comments from the gdb maintainers. I can do that if it looks like gcj or jvgenmain will be fixed. AG -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1427
next prev parent reply other threads:[~2005-08-08 15:20 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20001220121944.1427.tromey@gcc.gnu.org> 2003-08-03 20:14 ` [Bug java/1427] gcj should generate N_MAIN stab pinskia at physics dot uc dot edu 2003-08-03 20:16 ` [Bug java/1427] gcj should generate N_MAIN stab or DW_AT_entry_point dwarf2 debug info pinskia at physics dot uc dot edu 2003-11-03 18:19 ` aph at gcc dot gnu dot org 2005-08-08 11:28 ` aph at gcc dot gnu dot org 2005-08-08 15:20 ` green at redhat dot com [this message] 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 2005-08-09 4:11 ` woodzltc at sources dot redhat dot com 2005-08-09 4:18 ` Daniel Berlin 2005-08-09 4:19 ` dberlin at dberlin dot org 2005-08-09 7:04 ` woodzltc at sources dot redhat dot com 2005-08-24 6:09 ` 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=20050808151413.20652.qmail@sourceware.org \ --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: linkBe 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).