[openssl-dev] [openssl.org #4451] OS X 10.8, x86_64: 01-test_abort.t... sh: line 1: 71522 Abort trap: 6

Jeffrey Walton noloader at gmail.com
Sat Mar 19 01:49:05 UTC 2016

On Fri, Mar 18, 2016 at 9:46 PM, Richard Levitte via RT <rt at openssl.org> wrote:
> In this case, though, it's an application that explicitely calls an
> aborting function.  No subterfuge at all there, so if you wanted to
> complain, this is a particularly bad example.
> We do use OPENSSL_assert() in some places, to check *internal* state.
> When internal state is incorrect, it's not something that should keep
> running.  The aim is, of course, that such errors will be caught by
> our tests.

When the library aborts, what keeps sensitive information from being
written to disk and then sent to Apple, Microsoft, <favorite distro>
in a crash report?


More information about the openssl-dev mailing list