From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Introduce error_exit as a noreturn variant of error (EXIT_FAILURE, ...)
Date: Wed, 30 Mar 2022 16:43:08 +0200 [thread overview]
Message-ID: <ff3bb1dbe9a91cc9ad98b43eee1afc4f5ef4bb82.camel@klomp.org> (raw)
In-Reply-To: <20220327213215.397633-1-mark@klomp.org>
Hi,
On Sun, 2022-03-27 at 23:32 +0200, Mark Wielaard wrote:
> error (EXIT_FAILURE, ...) should be noreturn but on some systems it
> isn't. This may cause warnings about code that should not be
> reachable. So have an explicit error_exit wrapper that is noreturn
> (because it calls exit explicitly). Use error_exit in all tools
> under the src directory.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2068692
Pushed,
Mark
prev parent reply other threads:[~2022-03-30 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 21:32 Mark Wielaard
2022-03-30 14:43 ` Mark Wielaard [this message]
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=ff3bb1dbe9a91cc9ad98b43eee1afc4f5ef4bb82.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@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).