I don't understand how you could get different results, depending on
whether you select JDE=>Run App or C-c C-v C-r. Both are bound to the same
command. You say the application window fails to come up. Does the run
buffer come up in Emacs?
That is what baffles me most. Yet this is the behavior that observe. I do
get some startup message in the run buffer that application dumps and then
when system tries to display the initial window - which comes up blank. This
is to say that I get a opaque window and the file in the background is not
visible any more but window is empty and then everything (the java
application being executed) just dies. It never fails to start either from
debugger (both from menu or from keyboard shortcut) or from jde run option
in the menu or from command prompt - if that matters.
>2. Can we add prefix arguments to debugger commands like step.
>
Prefix arguments to do what?
Just to step that many times. We have this large java source file - 8400
lines and still growing and stepping in this is becoming too slow. I think
stepping speed is somehow related with the size of class file or source file
as I don't have same stepping problem with other files in the same process
which are of somewhat normal size. I would like to have prefix arguments so
that if I know I can execute next n statement until I want to examine the
results again - sort of setting a breakpoint after n statements and removing
the breakpoint after the statement is executed.
- Niranjan
