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.
Yes, I think that's it too. I experience it and posted
Would the problem be solved if comint returned code 1, instead of 129?
In other words, is the problem that comint returns an inappropriate
error code, or that comint returns *any* error code at all (i.e. it
shouldn't get an error from the subprocess in the first place)?
Raul
On Fri, 2004-10-08
Raul Acevedo wrote:
Would the problem be solved if comint returned code 1, instead of 129?
In other words, is the problem that comint returns an inappropriate
error code, or that comint returns *any* error code at all (i.e. it
shouldn't get an error from the subprocess in the first place)?
Len Trigg writes:
Raul Acevedo wrote:
Would the problem be solved if comint returned code 1, instead of 129?
In other words, is the problem that comint returns an inappropriate
error code, or that comint returns *any* error code at all (i.e. it
shouldn't get an error from the
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.
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
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
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,
I have set up jdb as my debugger and source directories for
debugger to '/dziela/java'.
Appending slash to the path name helped.
J.K.
I'm trying to debug with jdb and something goes
wrong with source tracking. I've created a simple
one file project in /dziela/java consisting of
of one class in foo.java. Whenever I start debugging,
debugger hits at the first line of foo.main, but
it tries to show the contents of ...
10 matches
Mail list logo
