At 03:39 PM 7/7/99 -0400, you wrote:
>Paul,
>
>Its clear that people need to debug more than one application concurrently.
>For me personally, the ability to debug multiple applications within the
>same debugger session would be sufficient. The only exception that comes to
>mind is debugging two apps which require different classpaths. But, I don't
>expect this to happen often, if ever.
>
>That said, one of your points was that multiple debugging sessions would
>require many emacs windows. But this is also true debugging multiple apps
Hi David,
That's true and that's why I wanted to put off multiple sessions per Emacs
instance until we have developed some experience with single debug session per
Emacs instance.
>within a single debugger. The first app debugged would create three
>windows, and each additional app would create two more. One for the
>standard IO and another for source. It could be difficult to manage all the
>windows.
>
>Another thought, why not allow users to start up new debugger sessions, and
>when they do, prompt for which socket port to use? The user supplies the
>port so jde doesn't have to track them. While I may never use this feature,
I thought of this but it seemed kind of reduntant as the debugger itself
will have the ability to start and manage multiple vm/debuggee processes.
You start to get a combinatorial explosion where you could theoretically
have multiple debugger sessions each managing multiple debuggee processes.
I just wonder whether all that flexibility is worth the design, implementation,
and usability headaches it entails.
What I'm suggesting is: let's get some experience with single
debuggee/Emacs instance
scenarious, work out what windows configurations are useful, how to save
and restore
configurations, etc., etc. Then once we learn what works and what doesn't in
terms of user interface as far as app I/O windows, debugger output windows,
stack browser windows, object inspector windows, etc., are concerned, we can
move on to implementing some kind of multiple debuggee per debugger/Emacs
instance.
Regards,
Paul
>it would provide flexibility for those who need multiple debugger sessions.
>
>I'm really looking forward to using this stuff. Thanks as always for
>everyone's effort.
>
>-Dave
>
>> -----Original Message-----
>> From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, July 06, 1999 12:44 PM
>> To: [EMAIL PROTECTED]
>> Subject: Debugger Instances
>>
>>
>> Hi all,
>>
>> I'm currently implementing the JDE interface to the new debugger being
>> developed for the JDE by Amit Kumar of Sun Microsytems. An issue has come
>> up on which I would like your advice. The issue is how many instances of
>> the debugger should the JDE allow. Theoretically, I could implement the
>> interface to allow you, the user, to launch as many instances as you want.
>> There are some problems with this, however. The first is complexity of
>> implementation. It would require me to assign and track socket numbers for
>> each debugger instance started. Also, it increase the complexity of the
>> user interface. Each session would have a minimum of three windows: a
>> source window, an application standard I/O window, and a debugger output
>> window. Thus, two sessions would entail six windows, three, nine, etcs.
>> Moreover, if you elect to browse stacks or an application's object
>> hierarchy, there would be even more windows. Managing the multiplicity of
>> windows would be a complex problem for the JDE and the user.
>>
