This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

java/1164: gcj 3.x generates bad DWARF 2 info

From: carlton at math dot stanford dot edu
To: gdb-gnats at sources dot redhat dot com
Date: 31 Mar 2003 19:12:12 -0000
Subject: java/1164: gcj 3.x generates bad DWARF 2 info
Reply-to: carlton at math dot stanford dot edu

>Number:         1164
>Category:       java
>Synopsis:       gcj 3.x generates bad DWARF 2 info
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          test-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 31 19:18:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     carlton at math dot stanford dot edu
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
GCJ 3.x generates bad DWARF 2 debug info.  For example,
the DW_AT_name entries for class members look like this:

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

instead of just this.

.long .LC2 # DW_AT_name: "main"

Until this gets fixed, debugging Java will be a dubious
proposition at best.

I've filed PR debug/10068 with the GCC folks about this.
>How-To-Repeat:

>Fix:

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

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]