-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Lee Moore on 1/27/2006 9:57 AM:
>
> I have made my own (local) changes to some of the cygwin sources in
> order to be able to provide the
> 'context' to 'sigaction' when an exception occurs (file diffs.txt
> attached).
Diffs are much eas
Hi Chris
This may be fixed in the latest snapshot, which I'm generating right now.
I checked out the source from CVS re-built and the fix you have made does
fix my reported problem.
Unfortunately it has uncovered another issue, I wonder if you could give
some advice.
I have made my own (lo
On Wed, Jan 25, 2006 at 10:19:14AM +, Lee Moore wrote:
>>>Mmm, IIRC signals can't be delivered unless you call cygwin functions.
>>
>>If that is actually true, it's a bug. Cygwin should be able to
>>interrupt user code. It doesn't try to interrupt...
>>
>>>int main(void) {
>>> signal(SI
Hi Chris, Samuel,
>Mmm, IIRC signals can't be delivered unless you call cygwin functions.
If that is actually true, it's a bug. Cygwin should be able to
interrupt user code. It doesn't try to interrupt...
>int main(void) {
> signal(SIGALRM,handler);
> alarm(1);
> Sleep();
>
On Mon, Jan 23, 2006 at 01:45:52PM +0100, Samuel Thibault wrote:
>Lee Moore, le Mon 23 Jan 2006 12:05:17 +, a ?crit :
>> I have an application which is creating generated code blocks in memory
>> provided by mmap, once the application is running in the generated code
>> blocks, it cannot be i
Hi,
Lee Moore, le Mon 23 Jan 2006 12:05:17 +, a écrit :
> I have an application which is creating generated code blocks in memory
> provided by mmap, once the application is running in the generated code
> blocks, it cannot be interrupted by a SIGALRM.
Mmm, IIRC signals can't be delivered u
Hi
I have an application which is creating generated code blocks in memory
provided by mmap, once the application is running in the generated code
blocks, it cannot be interrupted by a SIGALRM.
In the following example I generate a code section which simply performs an
infinite loop (using a
7 matches
Mail list logo
