From: Jeffrey Walton <noloader@gmail.com>
To: newlib@sourceware.org
Subject: Re: undefined references since newlib-3.2.0
Date: Sat, 13 Jun 2020 06:31:26 -0400 [thread overview]
Message-ID: <CAH8yC8mYzHe4u9xBa69xgtRph2kp9w6mCRO6ukNFeXtMw-m9mg@mail.gmail.com> (raw)
In-Reply-To: <20200612225013.GE15174@raven.inka.de>
On Fri, Jun 12, 2020 at 6:51 PM Josef Wolf <jw@raven.inka.de> wrote:
>
> On Fri, Jun 12, 2020 at 10:21:11AM +0200, Josef Wolf wrote:
>
> > To be honest, I completely fail to understand how this commit
> > https://sourceware.org/git?p=newlib-cygwin.git;a=commit;h=f88aece242178ff0c187d56e34a79645fbc44a23
> > can possibly cause those link failures. After all,
> > f88aece242178ff0c187d56e34a79645fbc44a23 shows no traces of abort/exit/kill/getpid.
>
> This patch replaces Balloc() by eBalloc() which calls __assert_func() on
> failure which in turn calls exit() and/or abort()
Please don't call abort(3).
My programs usually handle sensitive information. I need destructors
to run to ensure sensitive information is wiped. This is a compliance
item.
I also need to ensure sensitive information does not escape from the
application's security boundary. For example, the sensitive
information should not be written to the file system by way of a core
file; and it should not be egressed to an error reporting service for
the platform provider or application developer to inspect.
Jeff
prev parent reply other threads:[~2020-06-13 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 8:00 Wolf, Josef
2020-06-12 8:21 ` Josef Wolf
2020-06-12 22:50 ` Josef Wolf
2020-06-13 0:05 ` Keith Packard
2020-06-13 8:27 ` Josef Wolf
2020-06-13 17:20 ` Keith Packard
2020-06-14 14:50 ` Josef Wolf
2020-06-14 17:02 ` Keith Packard
2020-06-14 17:40 ` Brian Inglis
2020-06-14 20:13 ` Keith Packard
2020-06-15 4:53 ` Dimitrios Glynos
2020-06-16 3:43 ` Keith Packard
2020-06-17 11:36 ` Josef Wolf
2020-06-13 10:31 ` Jeffrey Walton [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=CAH8yC8mYzHe4u9xBa69xgtRph2kp9w6mCRO6ukNFeXtMw-m9mg@mail.gmail.com \
--to=noloader@gmail.com \
--cc=newlib@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).