[ECOS] GUI Config tool 2.04 bug (REPRODUCEABLE) - notclosing child process

[Trenton D. Adams]

That cygwin kill must not be working.  I run a cygwin shell and when gdb
locks up I have to close the shell because Ctrl-C or Ctrl-Z don't work.
cygwin does not kill the background arm-elf-gdb.exe.  So, it would
appear that the kill for cygwin is just as buggy as before.

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of Jonathan
Larmour
Sent: Monday, August 13, 2001 11:44 AM
To: Julian Smart
Cc: Trenton D. Adams; ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] GUI Config tool 2.04 bug (REPRODUCEABLE) -
notclosing child process


Julian Smart wrote:
> 
> At 09:08 AM 8/13/01 -0600, you wrote:
> >Start building a project and then try and cancel.  The config tool
> >doesn't kill make.exe cc1.exe or arm-elf-gcc.exe.
> >
> >I have some process killing code that I made for windows at home if
the
> >config tool doesn't have it already.  If you want it, let me know.
You
> >should have the process ID already anyhow when the processes are
> >spawned, but for some weird reason the config tool might not be able
to
> >close the child process.  If that happens my code should work.
> 
> Thanks -- there was some child-process code in the original CT which I
> should use but I'd also be interested to see your code in case it's
easier
> to understand :-)

If it's MSDN code we can't use it though....

Also, these are cygwin processes, so they should be killed in a "cygwin"
way so cygwin can do it's own correct cleanup. Is the new config tool
linking with the cygwin dll now? If so, perhaps using the cygwin kill
should be reliable now. When the original CT came out, cygwin kill was
unreliable, leading to extra complexity in the code.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062
Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine