This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: [patch] Fix oddity in personality routine
On Fri, Nov 27, 2009 at 02:20:32PM +0000, Bryce McKinlay wrote:
> I did take a quick look at this last week on my Mac and can confirm
> that there is a problem.
>
> A couple of observations:
>
> - It seems to effect ecj specifically, other EH tests from the libgcj
> testsuite seem to work ok.
> - An ecj built by hand (with "gcj -O0 -g ecj.jar
> --main=org.eclipse.jdt.internal.compiler.batch.GCCMain") also fails,
> so I don't think its a build related bug.
>
> Unfortunately, neither Apple's gdb nor a freshly build gdb 7.0 seem to
> work debugging binaries built by gcj head on darwin. gdb 7.0 insists
> the binary has no debugging info, and Apple gdb gets multiple "could
> not find partial DIE in cache" internal errors and "Previous frame
> inner to this frame (gdb could not unwind past this frame)" errors
> when you try to backtrace.
>
> If anyone knows how to get a working debugger for gcj on Darwin then
> perhaps we can debug this further.
>
> Bryce
>
>
> On Fri, Nov 27, 2009 at 10:52 AM, borlum <thomas@borlum.dk> wrote:
> >
> >
> >
> > Andrew Haley wrote:
> >>
> >> Not me, no. ?I don't have a Darwin system.
> >>
> >> Andrew.
> >>
> >
> > Oh, I guess I wasn't following the thread correctly.. :)
> >
> > I'm afraid I'm too new to the gcc source to fix it myself, I'll keep my
> > fingers crossed and sob quietly by myself in the meantime.
> >
> > Thomas
> >
> > --
> > View this message in context: http://old.nabble.com/-patch--Fix-oddity-in-personality-routine-tp26340585p26540778.html
> > Sent from the gcc - java mailing list archive at Nabble.com.
> >
> >
It may be helpful to apply the proposed patch to eliminate the problem
nulll AT_locations from the dwarf output in FSF gcc trunk...
http://gcc.gnu.org/bugzilla/attachment.cgi?id=19160
Currently, because of PR41473, either we are missing dSYM subdirectories in the build
or, when dsymutil doesn't actually crash, the resulting debug info is hosed. This issue
is fixed with the proposed patch, http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41473#c85,
so that we have proper debug info to walk through now.
Jack