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

Thu Dec 7 00:00:00 GMT 2006

Marco> That doesn't matter. The public API is the same. So as long as the
Marco> complete AWT/Swing API is provided on compilation, the classpath stuff
Marco> will be ignored (not pulled into the binary). That works without
Marco> problems...
Sorry, I thought you were merely using the peers, not replacing
awt+swing entirely. My mistake.
Marco> Crap! I hoped for some GCJ specific points because of AOT compilation.
It could be, but we don't have enough info to know, I'm afraid.
Marco> Calling initializeClass() through JNI while already in
Marco> initializeClass() should be ok?
Yes.
Marco> What about linux stacktraces? Is this a known problem?
Nope.
Tom