This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug java/11623] New: wrong debug file name info when compiling from .class
- From: "tromey at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Jul 2003 20:15:51 -0000
- Subject: [Bug java/11623] New: wrong debug file name info when compiling from .class
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11623
Summary: wrong debug file name info when compiling from .class
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tromey at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
A java .class file only contains the base name of its
corresponding source file. gcj copies this verbatim
into the resulting object file.
This means that when debugging with gdb I have to
add a large number of directories to the search path
to find all the .java files (in my scenario I can
only compile from .class files)
I think it would be useful if gcj instead prepended
the class' package, considered as a directory tree.
For example, if I compile "org/foo/bar/Doit.class",
right now gdb will end up looking for "Doit.java".
I'd prefer it to look for "org/foo/bar/Doit.java".
This isn't perfect, but it would greatly reduce the
number of "dir" commands I have to run, at least for
the most common way to structure java packages.