> At 10:06 AM 4/25/00 -0300, you wrote:
> >
> >Hi Paul,
> > ....
> >1. Expanding a local Character object to browse its fields times out at
> > 10, 20, and 60 second timeout limits. On the other hand, Integer
> > objects are fine.
> >
>
> Yes, there is something wierd about some of the static private fields of
> the character class. There declared as strings but they seem to be set to
> garbage. The debugger tries to expand the fields and gets choke by the
> resulting stream of characters. I was looking into this but got distracted.
> I'll get back to it ASAP.
>
Thanks for the explanation.
>
> >2. JDEbug --> Start Debugger --> Launch Process -->Set Breakpoint -->
> > Continue is fine, but
> >
> > JDE --> Debug App starts the JDEbug debugger, launches a process, sets
> > a breakpoint at the top of the program and and starts executing.
> > There seems to be a problem clearing breakpoints that have been
> > set in previous Launch Processes while in this mode.
> >
>
> This is not exactly what happens. There is a description of what Debug App
> does in the user's guide. Please read that and if it is not clear to you,
> let me know so that I can improve the description.
>
<<<<<< *********************************
I misphrased my question here is the confusion:
../jde-2.1.6beta23/doc/jdebug/ug/jdebug-ug-content.html
In this guide, a process refers to a running instance of an application.
JDEBug provides two commands for launching processes.
JDEbug->Processes->Launch Process
This command launches an instance of the application whose main class is
specified by the variable jde-run-application-class, or, if this variable
is nil, the application in the current Java source buffer. The application
stops at the first line of the application's main method, allowing you to
set breakpoints or begin stepping through the application.
====
The confusion is in the last line with the word `or'. It reads as if
you could start stepping through without setting a breakpoint. This is no
longer significant in beta23 since the step commands are now invisible but
it may be worth clarifying.
>>>>>>>>>>>>>>>> **********************************
> >3. I am curious about the mechanism for inspecting private instance
> > variables while debugging a class. I can browse the locals in methods
> > and constructors, but have to use the Evaluate Expression to
> > get the Object ID followed by Display Object to look at the instance
> > variables. Am I correct in this?
> >
>
> I'm not sure what you mean. The JDE now displays the "this" variable in the
> local buffer. ASAIK, you should see all the fields declared by the current
> class, including private fields.
>
Sorry, I based my question on beta22 and this must have been fixed in
beta23 since I now see the "this" variable and all is well.
> >4. I have received the following message Unbound slot: "#<class
> > jde-dbs-java-array>", "#<jde-dbs-java-array array 202>", length, oref
> > under question 3 after responding to Object ID: at the prompt.
> >
>
> I haven't paid much attention to the Display Object command since
......
>
Thanks again
>
> - Paul
>
Steven Rauch
Faculty of Computer Science
University of New Brunswick
Fredericton, N.B. E3B 5A5
Canada
