public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: carlton@math.stanford.edu
To: gcc-gnats@gcc.gnu.org
Subject: debug/10068: Java debug info for class members has wrong DW_AT_name
Date: Thu, 13 Mar 2003 23:56:00 -0000	[thread overview]
Message-ID: <20030313235025.13423.qmail@sources.redhat.com> (raw)


>Number:         10068
>Category:       debug
>Synopsis:       Java debug info for class members has wrong DW_AT_name
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 13 23:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     carlton@math.stanford.edu
>Release:        GCC 3.2
>Organization:
>Environment:
GCC 3.2 (with Red Hat 8.0; I have reason to believe this
bug is still present in mainline, but I haven't checked),
i686-pc-linux-gnu
>Description:
GCJ is generating incorrect DWARF 2 debug info for
members of classes (at least member functions, I
confess I haven't checked for member variables): the
DW_AT_name is "Class.member(args)" instead of just "member".

Hopefully 'break Class.member' will start working again
in GDB after this...
>How-To-Repeat:
Compile this file with gcj -gdwarf-2 -S -dA:

public class jmisc
{
  public static void main (String[] args)
  {
    return;
  }
}

Then look through the debug info to where main is
declared: you'll see

.long .LC2 # DW_AT_name: "jmisc.main(java.lang.String[])"

where it should just say

.long .LC2 # DW_AT_name: "main"

I'm attaching the full assembly file to the PR; lots
of the DW_AT_names are wrong, e.g. the constructors'
names are wrong in a different way. Some GCJ person
should perhaps talk to a G++ person about what the debug
info should look like.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-03-13 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 23:56 carlton [this message]
2003-03-14  0:16 David Carlton

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=20030313235025.13423.qmail@sources.redhat.com \
    --to=carlton@math.stanford.edu \
    --cc=gcc-gnats@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).