At 03:05 PM 8/20/99 -0400, you wrote:
>On Fri, 20 Aug 1999, Paul Kinnucan wrote:
>> Emacs and the debugger create a separate user interaction (comint) buffer
>for
>> each application that you launch. Anything that you type into the
>> buffer interaction window is relayed unfiltered to the standard input
>> of the application. Anything that the application outputs to standard out
>> or error is relayed unfiltered to the application's user interaction
>> buffer.
>> - Paul
>
>Does this mean you gave up using a socket to control the debugger ?
>Will this BUG/LIMITATION be present in the final version ?
>Did you avoid using a socket because of Windows users (no dialup...) ?
>
Why do you consider this a bug or limitation?
Here are the connections for a multiprocess debugging session:
JDEBug Buffer <--sio--> JDEBug
Process1 Buffer <--socket p1--> JDEBug <-- sio --> Process 1
Process2 Buffer <--socket p2--> JDEBug <-- mem --> Process 2
Process3 Buffer <--socket p3--> JDEBug <-- socket a1> Process 3
In this scenario, process 1 was launched by JDE/JDEBug, process 2 is
a local process attached through shared memory, and process 3 is a
remote process attached via a socket. JDEBug relays process standard I/O
between Emacs and the processes being debugged
- Paul
