Mail Archives: cygwin/2000/10/27/04:31:45
Jimen Ching wrote:
>
> Hi all,
>
> Can someone verify that the following patch is needed.
It's not needed since the `else' is ambiguous only in terms of parser,
not in terms of C. If the bracing doesn't force another order, `else'
binds to the latest `if'.
> Also, in exceptions.cc, there is a comment in interrupt_setup which says
> it is not multi-thread aware. I am running into a strange problem where I
> see an error about "couldn't send signal 14" and "wait for sig_complete
> event failed, ..." Are these related? Can someone give me some hints as
> to where to start looking if I want to know why these messages are showing
> up? Thanks.
Is this with the latest snapshot? If not try it with the latest
snapshot or the sources from CVS whatever you like more. Chris
has changed something related AFAIK.
If the problem resists, create a reproducable test case and debug
with gdb. After loading the symbol table of the dll with
`add-sym cygwin1.dll 0x61001000' you can set breakpoints etc. in the
DLL the same way as in your application. You should compile the
application with `-g', btw. If you doesn't change the settings
in the winsup source tree, the cygwin1.dll is compiled with `-g'
as well.
Corinna
> --------------------------------------------------------------------
> diff -u -r1.51 sigproc.cc
> --- sigproc.cc 2000/10/23 20:50:36 1.51
> +++ sigproc.cc 2000/10/26 03:47:13
> @@ -1121,10 +1121,12 @@
> * this thread should terminate.
> */
> if (rc == WAIT_TIMEOUT)
> + {
> if (!sig_loop_wait)
> break; // Exiting
> else
> continue;
> + }
>
> if (rc == WAIT_FAILED)
> {
>
> --
> Jimen Ching (WH6BRR) jching AT flex DOT com wh6brr AT uhm DOT ampr DOT org
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT sources DOT redhat DOT com
Red Hat, Inc.
mailto:vinschen AT redhat DOT com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -