At 06:59 PM 5/25/00 -0700, you wrote:
>Hi,
>I've just started to use JDE to debug. When I ran into an uncaught exception,
>I was able to see the call stacks via the jdb "where" command. As I moved
>up/down the stack using the up or down commands, I anticipated to see the
>corresponding source code file displayed with an arrow pointing to the right
>line but I didn't see that happening. Is this behavior expected or I don't
>have JDE set up correctly.
>
The JDE interface to jdb does not implement this functionality. I intend to
implement it at some point. Meanwhile, someone on this list recently
announced that he had done so. Perhaps you can get his patch. See the
archive. Alternatively, if you are using a JPDA-compatible vm, you might
want to consider using the JDE's integrated debugger, JDEbug, which is
included in the latest JDE beta. JDEbug not only moves the source pointer
but also shows the values of local variables in each stack frame.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
