This is the mail archive of the java@gcc.gnu.org mailing list for the Java 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]

Re: Are non-SJLJ exceptions busted on linux/x86?

From: David Daney <ddaney at avtrex dot com>
To: Scott Gilbertson <scottg at mantatest dot com>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, Mohan Embar <gnustuff at thisiscool dot com>, java at gcc dot gnu dot org
Date: Thu, 17 Nov 2005 13:54:57 -0800
Subject: Re: Are non-SJLJ exceptions busted on linux/x86?
References: <200511172029.jAHKTRUC019524@earth.phy.uc.edu> <49eb01c5ebbd$c903e870$3c16a8c0@mantatest.com>

Scott Gilbertson wrote:

dwarf2 exceptions are only ever required to work with dynamic linking as
there needs to be only one unwind functions and data.

I'm not sure I understand what you're saying.  Do you mean "the unwind
mechanism now only works with dynamic linking, because that makes the code
simpler"?

I think Pinski's assertion may be false. The dwarf2 unwinder used to work fine with static linking. Any regression from this behavior is clearly a bug.

And by static linking here, I am talking about libgcj only. I have no idea about what happens with statically linking everything (including glibc). The dwarf2 unwinder uses parts of the runtime linker to find the unwinding tables. If the runtime linker is not available then it might not work.

If you have a small stand alone test case, create a PR for it. I think it likely that someone would then fix it in short order.

David Daney

References:
- Re: Are non-SJLJ exceptions busted on linux/x86?
  - From: Andrew Pinski
- Re: Are non-SJLJ exceptions busted on linux/x86?
  - From: Scott Gilbertson

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