This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included

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 (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).
This appears to work fine except for the case when SIGALRM occurs.

it appears that for SIGALRM neither the _cygtls::call_signal_handler nor the _cygtls::handle_exceptions
get involved - is this correct ?

when my signal handler for the alarm is called I cannot get the context, it has clearly come through a
different path. What I need to do is change the cygwin code so that the context is saved when the SIGALRM
occurs, in the same way it is for my other exceptions

All suggestions welcome

Attachment: diffs.txt
Description: Text document

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]