From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Cc: Jon TURNEY <jon.turney@dronecode.org.uk>
Subject: [PATCH 0/3] Make detailled exception information available to signal handlers
Date: Tue, 31 Mar 2015 17:47:00 -0000 [thread overview]
Message-ID: <1427824014-19504-1-git-send-email-jon.turney@dronecode.org.uk> (raw)
Thanks for your help so far. Here's another attempt at this.
Questions:
The ContextFlags member of the CONTEXT type is named cr2 in struct __mcontext. I
don't understand how that can be right.
For a non-exception signal, we won't have aCONTEXT to provide. Is one that is
all zeroes acceptable?
Jon TURNEY (3):
Rename struct ucontext to struct __mcontext
Make mcontext and stack information available to signal handlers
Add cygwin_internal() operation to convert siginfo_t * to
EXCEPTION_RECORD *
winsup/cygwin/ChangeLog | 20 ++++++++++++++++++++
winsup/cygwin/exception.h | 1 +
winsup/cygwin/exceptions.cc | 20 ++++++++++++++++++--
winsup/cygwin/external.cc | 13 +++++++++++++
winsup/cygwin/include/cygwin/signal.h | 18 +++++++++++-------
winsup/cygwin/include/sys/cygwin.h | 4 +++-
winsup/cygwin/include/sys/ucontext.h | 26 ++++++++++++++++++++++++++
winsup/cygwin/include/ucontext.h | 16 ++++++++++++++++
8 files changed, 108 insertions(+), 10 deletions(-)
create mode 100644 winsup/cygwin/include/sys/ucontext.h
create mode 100644 winsup/cygwin/include/ucontext.h
--
2.1.4
next reply other threads:[~2015-03-31 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 17:47 Jon TURNEY [this message]
2015-03-31 17:47 ` [PATCH 3/3] Add cygwin_internal() operation to convert siginfo_t * to EXCEPTION_RECORD * Jon TURNEY
2015-03-31 19:11 ` Corinna Vinschen
2015-03-31 17:47 ` [PATCH 2/3] Make mcontext and stack information available to signal handlers Jon TURNEY
2015-03-31 18:46 ` Corinna Vinschen
2015-03-31 17:47 ` [PATCH 1/3] Rename struct ucontext to struct __mcontext Jon TURNEY
2015-03-31 18:37 ` Corinna Vinschen
2015-03-31 19:02 ` [PATCH 0/3] Make detailled exception information available to signal handlers Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1427824014-19504-1-git-send-email-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).