Michael Nielsen wrote:
>
> dan wrote:
> >
> > Try running with the "-nojit" option. Turning off the JIT allows the exception
> > stack trace to display line numbers.
>
> Where, I tried java -nojit in 1.2, but it complains that no such option.
>
> mvh
> mike.
>
The following options
dan wrote:
>
> Try running with the "-nojit" option. Turning off the JIT allows the exception
> stack trace to display line numbers.
Where, I tried java -nojit in 1.2, but it complains that no such option.
mvh
mike.
--
#include
---
On Mon, 19 Apr 1999 12:23:44 -0700, Jason Proctor wrote:
>Hi everyone,
>
>I've noticed that exception stack traces sometimes print helpful line
>numbers and sometimes print "Compiled Code" instead of line numbers. The
>latter is quite annoying when tracking down bugs and I was wondering what
>det
On Mon, Apr 19, 1999 at 12:23:44PM -0700, Jason Proctor wrote:
> Hi everyone,
>
> I've noticed that exception stack traces sometimes print helpful line
> numbers and sometimes print "Compiled Code" instead of line numbers. The
> latter is quite annoying when tracking down bugs and I was wondering
The VM Spec says that the LineNumberAttribute can be ignored; any such
information that the VM provides is a function (IMHO) of the
completeness of the debugging implementation in the VM. Not sure that
answers your question
--troy
On Mon, 19 Apr 1999, Jason Proctor wrote:
Hi eve
Hi everyone,
I've noticed that exception stack traces sometimes print helpful line
numbers and sometimes print "Compiled Code" instead of line numbers. The
latter is quite annoying when tracking down bugs and I was wondering what
determines whether line numbers are included or not. It seems to be
Try running with the "-nojit" option. Turning off the JIT allows the exception
stack trace to display line numbers.
Jason Proctor wrote:
> Hi everyone,
>
> I've noticed that exception stack traces sometimes print helpful line
> numbers and sometimes print "Compiled Code" instead of line numbers
