From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: sigsegv: Document context type for DragonFly BSD
Date: Tue, 08 Jun 2021 03:24:25 +0200 [thread overview]
Message-ID: <4331462.r8KLvGdi8Y@omega> (raw)
On DragonFly BSD, sigsegv.c uses a 'struct sigcontext *'. This won't change
soon, since DragonFly BSD supports only one architecture: x86_64.
2021-06-07 Bruno Haible <bruno@clisp.org>
sigsegv: Document context type for DragonFly BSD.
* lib/sigsegv.in.h (stackoverflow_context_t): On DragonFly BSD, it is a
pointer to 'struct sigcontext'.
diff --git a/lib/sigsegv.in.h b/lib/sigsegv.in.h
index e442f4d..9253766 100644
--- a/lib/sigsegv.in.h
+++ b/lib/sigsegv.in.h
@@ -186,7 +186,7 @@ extern int sigsegv_leave_handler (void (*continuation) (void*, void*, void*), vo
|| defined __CYGWIN__ || defined __HAIKU__
typedef ucontext_t *stackoverflow_context_t;
# elif defined __GNU__ \
- || defined __FreeBSD_kernel__ || (defined __FreeBSD__ && !(defined __sparc__ || defined __sparc64__)) \
+ || defined __FreeBSD_kernel__ || (defined __FreeBSD__ && !(defined __sparc__ || defined __sparc64__)) || defined __DragonFly__ \
|| defined __OpenBSD__ || defined __sgi
typedef struct sigcontext *stackoverflow_context_t;
# else
reply other threads:[~2021-06-10 20:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4331462.r8KLvGdi8Y@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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).