Re: natClass.cc, java::lang::Class::initializeClass() problems

[Marco Trudel <mtrudel at gmx dot ch>]

Andrew Haley wrote:
> Marco Trudel writes:
>  > 
>  > Any ideas from the professionals?
>
> It is possible that Sun's AWT/Swing implementation is written entirely
> in portable Java.  However, I doubt it.  The core Java libraries are
> fairly tightly coupled to a particular VM interface and to each other;
> they tend share assumptions about implementation details.
>
> When we have the sources for Sun's Java libraries we'll be able to see
> where the non-portable assumptions are.
>
> What you are doing is, more or less, akin to taking a telephone
> exchange from New York and dropping it into Tokyo.  If it doesn't
> work, then you'll have to break out the debugger and find out why it
> doesn't work.  But I would urge you to use free software instead.

Actually we already have the source and I'm working with them. Ok, it's 
not GPL, but it's the SUN COMMUNITY SOURCE LICENSE and I think it's ok 
for what I'm doing...
Besides the source thing, I would assume importing AWT/Swing to work as 
easily as SWT. Because, after all, it's nothing different. Just a 
framework with some native libraries...


> With regard to non-functional stack traces on Windows: this is a known
> problem that'll be fixed once we get DWARF unwinder data on that
> platform.  With regard to Linux: they should work, but it's possible
> that there is a bug.  If you can reproduce the bug using free
> software, let us know.

I will create a bugreport as soon as I have a trivial example.


thanks
Marco