Hello,
On linux fedora-core-2 I get a Comint exited abnormally with code 129
error message when trying to debug any java app with jdee:
Comint exited abnormally with code 129
NB: the same jdb command submitted in a shell runs fine.
NB: I don't get this error on MacOS X using the same
patrick duval writes:
Hello,
On linux fedora-core-2 I get a Comint exited abnormally with code 129
error message when trying to debug any java app with jdee:
Comint exited abnormally with code 129
NB: the same jdb command submitted in a shell runs fine.
NB: I don't get
/ Paul Kinnucan [EMAIL PROTECTED] was heard to say:
| Which version of the JDK are you using?
1.2.2 on Linux.
Be seeing you,
norm
--
Norman Walsh [EMAIL PROTECTED] | [They] say the Earth is flat, but I
/ Paul Kinnucan [EMAIL PROTECTED] was heard to say:
| Norman Walsh writes:
| / Paul Kinnucan [EMAIL PROTECTED] was heard to say:
| | Which version of the JDK are you using?
|
| 1.2.2 on Linux.
|
| Does setting jde-db-debugger to oldjdb help?
Thanks, Paul. That helped (some). I now get
Norman Walsh writes:
/ Paul Kinnucan [EMAIL PROTECTED] was heard to say:
| Norman Walsh writes:
| / Paul Kinnucan [EMAIL PROTECTED] was heard to say:
| | Which version of the JDK are you using?
|
| 1.2.2 on Linux.
|
| Does setting jde-db-debugger to oldjdb help?
I am using the latest beta version of JDE ( jde-2.2.7beta5 ) with
the latest components.
I take these steps:
JDEbug-Processes-Start Debugger
JDEbug-Processes-Launch Process
I then set a breakpoint
JDE-Debug App
error in mini-buffer:
Invalid slot name: "#jde-dbs-proc process1", field
Submit a problem report.
- Paul
