From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v2 1/2] setjmp: Use BSD sematic as default for setjmp
Date: Mon, 07 Aug 2023 21:51:56 +0200 [thread overview]
Message-ID: <87cyzyeilf.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b501a980-681e-eb48-f596-af93cf9495c5@linaro.org> (Adhemerval Zanella Netto's message of "Mon, 7 Aug 2023 15:33:39 -0300")
* Adhemerval Zanella Netto:
> I still think unblocking the signal on raise is not fully correct, since
> calling abort in the SIGABRT handler itself leads to a recursive call
> to the handler, which will eventually lead to a stack overflow.
We can't know that, it depends on how the handler is written.
I think it's better to call the handler at least once (even if the
signal was blocked) and risk terminating with SIGSEGV due to recursive
signals.
Thanks,
Florian
next prev parent reply other threads:[~2023-08-07 19:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 17:34 [PATCH v2 0/2] Make abort AS-safe Adhemerval Zanella
2023-08-03 17:34 ` [PATCH v2 1/2] setjmp: Use BSD sematic as default for setjmp Adhemerval Zanella
2023-08-03 18:06 ` Joe Simmons-Talbott
2023-08-03 22:09 ` Joseph Myers
2023-08-04 8:43 ` Florian Weimer
2023-08-04 12:36 ` Adhemerval Zanella Netto
2023-08-05 7:21 ` Paul Zimmermann
2023-08-07 12:54 ` Florian Weimer
2023-08-07 12:59 ` Adhemerval Zanella Netto
2023-08-07 13:40 ` Florian Weimer
2023-08-07 18:33 ` Adhemerval Zanella Netto
2023-08-07 19:51 ` Florian Weimer [this message]
2023-08-07 20:49 ` Adhemerval Zanella Netto
2023-08-03 17:34 ` [PATCH v2 2/2] stdlib: Make abort AS-safe (BZ 26275) Adhemerval Zanella
2023-08-03 18:05 ` Joe Simmons-Talbott
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=87cyzyeilf.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).