Here are some backtraces:
snapshot: cygwin1-20100707.dll.bz2
System AMD64 CPU - Windows XP Professional 64 bit Edition, Version 2003,
Service Pack 2
Program is test_case_1_sleep.c:
1 /**
2 * small test program whether signals between threads work as they should
3 */
4
5 #include
6 #incl
> Signal generation and signal delivery aren't the same thing. With
> asynchronous signals as in your test case, there's always some sort of
> delay until the signal is delivered, and I don't know whether the
> standard actually requires any upper bound on that. One example where
> a signal in Cygw
Hi
I did read your other response, regarding the signal developer being on
vacation. I'm sending this just for reference, since I had already
looked it up anyway :)
Andy wrote:
> Have you got chapter and verse from the POSIX standard on that? By
> 'interrupt' do you mean SIGINT or any signal? Is
FYI
Just to update some details.
I am working with James Cotton on the OpenPilot project.
We are trying to port the POSIX simulation port of FreeRTOS to cygwin.
We run into issues with signal handling in cygwin 1.7.5 that are
currently blocking our development, since every method to suspend a
ru
4 matches
Mail list logo
