GCC Bugzilla – Bug 11623
wrong debug file name info when compiling from .class (lacks directories)
Last modified: 2005-07-23 22:39:30 UTC
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.
I think is a bad bug which should be fixed for 3.4, right?
I'm unsetting the target milestone again.
This is annoying, but it isn't a regression and there is a known
workaround -- just enter a lot of "dir" commands in gdb.
There are worse java debuginfo bugs out there, namely