Current gcj on powerpc

Sat Aug 3 15:48:00 GMT 2002

Hi,
On Fri, 2002年08月02日 at 08:08, Bryce McKinlay wrote:
> Mark Wielaard wrote:
>> >>Can you place a breakpoint on abort() and find out what the
> >>_Unwind_Reason_Code is? The comment suggests it could be
> >>_URC_END_OF_STACK or some other failure.
> >> 
> >I am really not that good with gdb. I can set the breakpoint on
> >exception.cc:110 but the gdb tells be there is no variable code (why, it
> >is right there?) Any idea how I can get at it:
> > 
> You need to build the file that you're debugging without optimization 
> for GDB to work properly. The easiest way to do that is to "touch 
> exception.cc" and rebuild libjava with "make CXXFLAGS=-g"

Thanks, of course the compiler optimizes the assignment away since it is
never used. But now that I can print it it doesn't make sense:
 110	 abort();
 (gdb) print code
 1ドル = 268705696
Which doesn't make sense since only value 0 till 8 are meaningfull
according to unwind.h. Sigh.
I have been readding the patch is parts and it seems that the DSA
provider classes are to blame (I can add all other changes and new
classes without problem). But compiling on my powerpc machine is very
slow so it might take a while till I have found out exactly which of the
following classes causes this strange behaviour:
DSAKeyPairGenerator.java
DSAParameterGenerator.java
DSAParameters.java
DSASignature.java
GnuDSAPrivateKey.java
GnuDSAPublicKey.java
Cheers,
Mark