[259] in java-interest
Re: debugging applets
daemon@ATHENA.MIT.EDU (Jonathan Payne)
Fri Jun 9 18:50:28 1995
Date: Fri, 9 Jun 1995 15:30:51 -0700
From: jpayne@starwave.com (Jonathan Payne)
To: jsparkes@bnr.ca
Cc: java-interest@java.sun.com
In-Reply-To: <"29324 Fri Jun 9 17:14:19 1995"@bnr.ca> (jsparkes@bnr.ca)
> Date: Fri, 9 Jun 1995 17:13:00 -0400
> Content-Identifier: debugging app...
> From: "jeff (j.d.) sparkes" <jsparkes@bnr.ca>
> Sender: owner-java-interest@java.sun.com
> Precedence: bulk
> X-Info: To unsubscribe, send 'unsubscribe' to java-interest-request@java.sun.com
> Content-Type: text
> Content-Length: 720
>
> I've finally written enough java code to start debugging. There's doesn't
> seems to be a lot of support for it. The best I get is a stack traceback
> in in my HotJava weblog file.
Use System.out.println("message");
Fire up hotjava like this:
java browser.hotjava
and standard output won't get redirected to a file.
> There are a couple of problems:
> 1. the -l option to java-a3 to set the logging level doesn't work. And
> there's no documentation of what the levels are.
This is logging at the C level - monitor enter, monitor exit, etc.
You don't care about this at all. And it only works with the debug
version of java: java_g.
> 2. System.traceMethodCalls(1) doesn't do anything either.
This works, but it only works for java_g.
> I'd like to hear how the current java developers debug. And I think there
> should be a section on it in the programmers guide.
System.out.println rules!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Hey - you'd be amazed how far you can get with it :-) I understand a
debugger is on its way.
> --
> Jeff Sparkes
> jsparkes@bnr.ca Bell-Northern Research, Ottawa, Ontario, Canada
> -
> Note to Sun employees: this is an EXTERNAL mailing list!
> Info: send 'help' to java-interest-request@java.sun.com
>
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
