wierd top bug = problem with commune_send

Christopher Faylor cgf@redhat.com
Thu Jun 12 17:32:00 GMT 2003

On Thu, Jun 12, 2003 at 06:29:32PM +0100, Chris January wrote:
>The problem reported on the Cygwin mailing list as "wierd top bug" appears
>to be due to a problem in commune_send. commune_send gets stuck in a busy
>loop waiting for the reply to the _SIGCOMMUNE signal when the signal is sent
>to a Windows process as opposed to a Cygwin process. The Windows process
>doesn't understand signals so doesn't reply to it - and commune_send gets
>stuck in the busy loop at line 365. I don't have time to actually craft a
>fix at the moment I'm afraid.

commune_send is not *supposed* to be communicating with a non-cygwin
process.  How is it possible for there to be a _pinfo structure for a
non-cygwin process?


More information about the Cygwin-developers mailing list