public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "woodzltc at sources dot redhat dot com" <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: Tue, 09 Aug 2005 07:04:00 -0000	[thread overview]
Message-ID: <20050809070423.14572.qmail@sourceware.org> (raw)
In-Reply-To: <20001220121944.1427.tromey@gcc.gnu.org>


------- Additional Comments From woodzltc at sources dot redhat dot com  2005-08-09 07:04 -------
(In reply to comment #15)

[snip]

> Please add an issue on dwarf.freestandards.org and i'll take it from
> there.
 
I had added an public comment titiled "add a new entry to identify the main
function in a program", but it didn't return me an issue number.  Maybe it is
due to the fact that I didn't fill section number and page info. (the reason is
that I don't know which section if apply to).  Do I need to fill all the fields?  

If you can't see that, I will try again with a bogus section and page.

-- 


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


  parent reply	other threads:[~2005-08-09  7:04 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
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 [this message]
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=20050809070423.14572.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).