[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Debugger and Win98
|
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_001F_01C2F2B8.EE271C40
> Content-Type: text/plain;
> charset="koi8-r"
> Content-Transfer-Encoding: quoted-printable
>
> Hi all!!!
>
> I found a strange behavior of Java in some cases while debugging C/C++ =
> projects. I have to say that this behavior can be seen only on Win98.=20
> While debugging program can be in "stopped" or in "running" condition. =
> When I press "Terminate" button in "stopped" condition everything is ok =
> but if I press "Terminate" in "running" condition fatal error of =
> operation system occurs.=20
> With help of Java Debugger I found out that error occurs in =
> MISession.terminate() while launching following string:
> gdbProcess.destroy();
>
> As I understood the reason of this error completely depends on Java( =
> sometimes a diagnostic appeares: JVM terminated Exit code =3D -1 )
>
> May be someone met this problem an can prompt how to avoid it?
Do you have a .log file entry, that would be handy.
I'm not familiar with Win does platform but if the target is running
gdbProcess.destroy() will try to send a few signal to the gdb to kill it
INT and TERM then simply closing the pipe stream.
This is local ? using Cygwin ?
