At 10:25 AM 2/4/00 -0500, you wrote:
>The starting problem I'm having seems to boil down to this:
>
>In 1.3rc1, if i use javac, JDEBug won't stop at a breakpoint set in main
>of the following class. With jdb.exe it works (the JPDA version of
>jdb).
>
JPDA supports two methods of specifying breakpoints:
* qualified class name and source file line number, e.g.
break at com.foo.Bar 123
* and file name and line
breadk at bar.java 123
The first method has been supported since JDK 1.0. The second
method was introduced with the JPDA. The purpose of the second method
is to allow you to set breakpoints in inner and anonymous inner classes
without having to do complicated parsing of the source file. When I started
developing JDEBug last summer, Sun's JPDA team suggested that I use the new
method, so I did and in fact the current version still uses it. It appears,
however, that this method does not work for inner classes as advertized and
has other problems. Someone on the list reported that this ia a bug that
the JPDA has promised to fix for JDK 1.3. Apparently it is not. I am therefore
planning to revert to the old class/line no spec used by jdb. This should
clear up the problem and allow setting breakpoints in named inner classes
(anonymous inner classes are really hard to spec so that will have to
come later, if at all). The latest beta of the JDE alreay supports setting
breakpoints in named inner classes when using jdb. I'll simply retrofit the
code to JDEbug in an upcoming release.
- Paul
