At 10:25 AM 7/6/99 -0700, you wrote:
>
>> the main method. From this point on, you will not be allowed to debug any
>> other applications until you stop the current application. When you stop
>> debugging of an application, the JDE leaves the debugger running, thereby
>> reducing startup time the next time you want to debug an app.
>>
>> Later on, you will be able to start another application even when a current
>> app is running. The debugger will assign a process id to each app/process
>> that you start and the JDE/Debugger interface will use that ID to route
>> commands and I/O to the appropriate process.
>
>These two paragraphs seem to contradict each other. The first says no
>debugging
>other apps until you stop the current app (BTW, what does STOP mean -
>terminate?).
> The second says you can start another app even when
>another is running - huh?
>
Hi Harold,
I meant "later" as in a subsequent release of the JDE/Debugger, i.e., the
initial
release (August?) would support debugging one process at a time per Emacs
session;
a subsequent release (Oct./Nov?0 would support debugging multiple processes
per Emacs session via the same debugger instance.
>FYI: I use multiple debugging sessions everyday - usually two,
>sometimes three.
>I work on the CORBA stuff in the JDK. I generally have one session
>stepping through
>client code and another stepping through server side (and sometimes a
>third watching the
>ORBD). I cannot "stop" the client side so I can begin debugging the
>server
>side. I really need them both at once.
>
Would it be possible for you to run two Emacs/debugger sessions. The JDE will
allow you to configure the socket numbers so you could specify a different
socket for each session.
- Paul
