>
> So it seems to be something with exception handling. In the two cases
> below I had to take care to avoid class-lookup failures. Avoiding
> those failures, the gcj shared object loads and runs fine.
>
Yes, it sounds so familiar. Looking for these non-existent classes
is the first exception kaffe throws and catches when it starts up.
It means that no exceptions work. But see my other mail.
On the positive side, it's nice to see someone actually replicate
what I did and getting that far.
- Godmar
- crash loading gcj stuff Marcus G. Daniels
- Re: crash loading gcj stuff Godmar Back
- Re: crash loading gcj stuff Alexandre Oliva
- Re: crash loading gcj stuff Marcus G. Daniels
- Re: crash loading gcj stuff Godmar Back
- Re: crash loading gcj stuff Alexandre Petit-Bianco
- Re: crash loading gcj stuff Marcus G. Daniels
- Re: crash loading gcj stuff Godmar Back
- Re: crash loading gcj stuff Marcus G. Daniels
- Re: crash loading gcj stuff Godmar Back
- Re: crash loading gcj stuff Godmar Back
- Re: crash loading gcj stuff Archie Cobbs
- Re: crash loading gcj stuff Marcus G. Daniels
- Re: crash loading gcj stuff Godmar Back
- Re: crash loading gcj stuff Marcus G. Daniels
- Re: crash loading gcj stuff Godmar Back
