At 12:38 PM 7/20/99 -0600, D'Elia, Kevin E. wrote:
>Actually, I wasn't supplying the classpath as an argument to "use" - I
>simply started everything up, typed in "use" (as the example shows) and the
>*output* of the use command without parms was my classpath...
>
>Stopped at line 40 in ReportDataLoader.java
>main[1] running ...
>main[1] use
>d:\jdk1.1.6\lib\classes.zip;d:\Frame\classes
>main[1] list
>Unable to find ReportDataLoader.java
>main[1]
>
>After I got these results, the error of my ways was pointed out to me by
>another kind soul...he told me that I was specifying the package information
>along with the top-level directory, so when I was typing in "use
>d:\Frame\src\com\..\.." and so on, I should have only typed in
>"d:\Frame\src" and the package level stuff would be picked up...anyhow, this
>turned out to be of little use to me in my efforts, since "list" shows only
>source code from the currently debugged class file...if I want to be able to
>do what I want, I had to look elsewhere...fortunately, reading the
>documentation helped (I overlooked something when I tool the link for
>specifying subdirectories, but then came back to it when I wasn't able to
>set breakpoints in other source), and now I am able to do what I want...one
>point still remains, and that is the transient nature of the breakpoints...I
>don't see anywhere that they are persistent across sessions (project file or
>other means)...how can this easily be accomplished (other than saving the
>jdb buffer off to a file, then cutting and pasting the stop <at|in> commands
>into the jdb buffer?
>
Persistant breakpoints will be a feature of the new Java debugger being
developed jointly by me and Sun for use with the JDE.
We expect to have a basic version ready for user testing within the next
few weeks.
- Paul
