From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 46988@debbugs.gnu.org
Subject: bug#46988: 28.0.50; Documenting and verifying assumptions about C code not calling quit or GCing
Date: Mon, 08 Mar 2021 20:42:46 +0100 [thread overview]
Message-ID: <875z21mnyh.fsf@gnus.org> (raw)
In-Reply-To: <CAOqdjBc4_rzuCZzM6ZTrc7FeanYDj=bVByuxs7tfub=AdeaDGw@mail.gmail.com> (Pip Cet's message of "Sun, 7 Mar 2021 14:06:01 +0000")
Pip Cet <pipcet@gmail.com> writes:
> Patch attached. It assumes the standard stack growth direction, and
> that __builtin_frame_address (0) is available and works. Uses GCC's
> __attribute__ ((cleanup (...))).
>
> My point here is that the technical implementation isn't the problem,
> the question is whether we're disciplined enough to run with checking
> enabled and react to bug reports about the fatal error being thrown.
This is something that comes up again and again, so having
infrastructure to getting feedback faster on this stuff sounds like a
good idea to me.
Even better would be to have build-time warnings, but I guess that's
pretty much impossible?
On the other hand, even if this just gives us run-time feedback, I guess
the test suite would give some coverage here...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-08 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 13:47 bug#46988: 28.0.50; Documenting and verifying assumptions about C code not calling quit or GCing Pip Cet
2021-03-07 14:06 ` Pip Cet
2021-03-08 19:42 ` Lars Ingebrigtsen [this message]
2021-03-08 19:57 ` Pip Cet
2021-03-09 14:05 ` Lars Ingebrigtsen
2021-03-10 18:28 ` Matt Armstrong
2021-03-10 19:09 ` Pip Cet
2021-03-11 23:17 ` Matt Armstrong
2022-06-20 1:41 ` Lars Ingebrigtsen
2022-06-20 11:47 ` Eli Zaretskii
2022-06-23 15:56 ` Pip Cet
2022-06-23 16:08 ` Eli Zaretskii
2022-06-23 16:20 ` Mattias Engdegård
2022-06-23 16:35 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875z21mnyh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46988@debbugs.gnu.org \
--cc=pipcet@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).