At 05:51 PM 3/27/00 +0200, you wrote:
>Hi!
>
>I have experienced some strange behavoiur while using JDebug, have
>anyone else experienced the same things (i.e. are these things already
>reported as bugs?)?
>
>I'm using JDE-2.6.b21 on Solaris 2.6, JDK 1.2.2, GNU-Emacs 20.5.
>
>First a question about the semantics related to "step into" and "step
>over". If I have code like this
>
>Foo foo = new Foo(bar, gazonk);
>
>What sequence of "step into" and "step over" should I use to reach the
>constructor of Foo without first visiting the base class of Foo or the
>class loader? Or is the easiest way simply to put a break point in Foo's
>constructor?
>
This is the only solution for the moment. In a future release, the JDE will
allow you to filter out "noise" classes when stepping through code.
>OK. Now for the features/bugs
>
>* I had set breakpoints in several classes located in individual files.
>After the debugsession was over I removed some of the break points and
>started over. The break points were removed via the JDebug menu. The
>problem was that this did not propagate fully, so those break points
>still existed, but were not visible in the buffer. The breakpoints can't
>be removed, even if I restart the debugger.
>
This sounds like a bug. I'll look into this.
>* After makeing some changes to the code (resulting in new lines beeing
>added) and recompilation, the debugger still thought that a break point
>was on line n, when it actually was on line n+2 (i.e. I had added 2 new
>lines above the breakpoint).
>
Yes. The JDE does not currently keep track of editing changes in the source
buffer. Implementing this seems to be a bit complicated so I probably won't
get to it until the 2.1.7 release.
>* I started my debug session in the buffer Foo.java which then took me
>to Bar.java. I got an exception which was printed to stdout, so I
>selected JDebug -> Show Buffer -> CLI. Then the buffer arrengement
>reverted back so I was in the Foo.java buffer again with the correct CLI
>buffer.
>
Yes. This is a bug that I haven't gotten around to fixing yet.
>* When I single step with "step over" and an exception ocurrs, I am
>immediatly transfered to the apropriate catch clause, which might be
>very far from the method I am in. I think JDebug should let me inspect
>the values of all local variables before moving out of scope...
>
I'll look into this.
Thanks very much for the feedback. It is very helpful.
Regards,
Paul
------------------------------------------------------------
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
Please use JDE->Help->Submit Problem Report when reporting a bug or seeking
help. This will insure that you include all information that may be
required to solve your problem.
