I don't diagree, the kernel should not oops.
I just was not sure if you were testing the kernel or the JVM.
Dave
Juergen Kreileder wrote:
David D. Lucas <[EMAIL PROTECTED]> writes:
My guess is the JVM is compiling byte code into machine code. The
JIT compiler is probably producing b
My guess is the JVM is compiling byte code into machine code. The JIT
compiler is probably producing bad code for your platform. If you want
to just run Java without the JIT, try using the -Xint (interpreted mode
only) option. This should not crash while running. If that works, then
you can
You may have already checked this, but see if the Window Behavior for
the window manager is "Focus follows Mouse".
Set it to an alternative like "Click To Focus".
It could be something with the window manager.
Best Wishes,
Dave
Matt Avery wrote:
I have had some very strange problems running Jav
Yang,
This is probably not the correct place to ask a vendor specific question
unrelated to the JVM.
However, try looking at the FAQ from http://www.borland.com/jbuilder .
(Hint: look under the bin directory)
Best Wishes,
Dave
--
+
I use TogetherJ without a problem (single i686). I am using both
Blackdown JDK 1.2.2 RC4 and Sun JDK 1.3 beta. First try running with JIT
disabled. Also, make sure you are picking up the right JVM as it runs.
When it first comes up, expecially TJ 4.0, you should be able to see the
JVM that is r
Kontorotsui wrote:
>
> aClass extends aSuperClass
> {
> final int v = 1;
>
> aClass()
> {
> super(v);
> }
> }
First off, my understanding of the question is why doesn't v exist when
passed into super. "super" is not a method call like everything else.
It is a special keyword and a
