debugging with jdb

2004-10-05 Thread Raul Acevedo
I haven't debugged with JDE in a while, so I don't know if this is a new bug with the latest JDEE beta. Every time I display an expression with jdb, the debugger exits. Is this a known issue? It will display the expression just fine, and then exit with Comint exited abnormally with code 129.

debugging with jdb

2004-10-05 Thread Paul Kinnucan
Raul Acevedo writes: I haven't debugged with JDE in a while, so I don't know if this is a new bug with the latest JDEE beta. Every time I display an expression with jdb, the debugger exits. Is this a known issue? It will display the expression just fine, and then exit with Comint

RE: Feedback needed on w3m support

2004-10-05 Thread Nascif Abousalh-Neto
I had this same problem; we solved it by configuring JDEE to create the temporary pages in a directory relative to the user's home, something like ~/tmp, instead of the default /tmp. Regards, Nascif -Original Message- From: Heinz-Dieter Conradi [mailto:[EMAIL PROTECTED] Sent:

Re: debugging with jdb

2004-10-05 Thread Raul Acevedo
On Tue, 2004-10-05 at 15:18 -0400, Paul Kinnucan wrote: No this is a problem with Comint on some combinations of Emacs and the host operating system. I believe it may have something to do with how comint handles standard error input from an external process, e.g., jdb. It's my impression that

Re: debugging with jdb

2004-10-05 Thread Paul Kinnucan
Raul Acevedo writes: On Tue, 2004-10-05 at 15:18 -0400, Paul Kinnucan wrote: No this is a problem with Comint on some combinations of Emacs and the host operating system. I believe it may have something to do with how comint handles standard error input from an external process,