History log of /openbsd-src/regress/lib/libc/explicit_bzero/explicit_bzero.c (Results 1 – 9 of 9)
Revision Date Author Comments
# aa487188 10-Feb-2022 tb <tb@openbsd.org>

If running with ASAN, mark test_with{,out}_bzero() with the
no_sanitize_address attribute. ASAN doesn't seem to be able
to understand these lowlevel gymnastics with sigaltstack()
and segfaults in __i

If running with ASAN, mark test_with{,out}_bzero() with the
no_sanitize_address attribute. ASAN doesn't seem to be able
to understand these lowlevel gymnastics with sigaltstack()
and segfaults in __intercept_memem().

This allows LibreSSL and other portable projects that use this
test run tests with ASAN enabled.

Issue reported and workaround suggested by Ilya Shipitsin

Paraphrasing millert: it's a little ugly but it's only a regress.

show more ...


# 08218f21 09-Feb-2022 tb <tb@openbsd.org>

silence "function declaration isn't a prototype" warning by changing
int foo() to int foo(void)


# c781ba80 27-Mar-2021 bcook <bcook@openbsd.org>

Handle dynamic definition of SIGSTKSZ as of glibc 2.34 on Linux.

ok bluhm@, inoguchi@, tb@, deraadt@


# ff84e1f9 11-Jul-2014 matthew <matthew@openbsd.org>

Fix dumb copy/paste mistake.

Noticed testing with clang.


# ccf34311 11-Jul-2014 matthew <matthew@openbsd.org>

Fix explicit_bzero regress for Solaris and OS X compatibility

Solaris and OS X clobber the signal stack when returning to the main
stack, which caused the original testing strategy (inspecting the
s

Fix explicit_bzero regress for Solaris and OS X compatibility

Solaris and OS X clobber the signal stack when returning to the main
stack, which caused the original testing strategy (inspecting the
signal stack once we're back on the main stack) to fail.

To be compatible with this behavior, the regress test now inspects the
signal stack space while we're still executing on it. This is a bit
iffy because we might clobber it ourselves while inspecting it, but we
as long as its not completely clobbered we should be okay.

thx bcook for the Solaris test account

show more ...


# 6211cbf5 09-Jul-2014 matthew <matthew@openbsd.org>

Add some extra sanity checks to make sure the test functions actually
run on altstack.


# 475bbe2e 09-Jul-2014 matthew <matthew@openbsd.org>

Better workaround for OS X sigaltstack() bug

OS X's sigaltstack() fails with ENOMEM if ss_size < MINSIGSTKSZ even
if SS_DISABLE is specified in ss_flags. Rather than add code to try
to cope with th

Better workaround for OS X sigaltstack() bug

OS X's sigaltstack() fails with ENOMEM if ss_size < MINSIGSTKSZ even
if SS_DISABLE is specified in ss_flags. Rather than add code to try
to cope with this stupidity, just don't bother restoring the original
signal stack.

show more ...


# 42cbf0f7 09-Jul-2014 bcook <bcook@openbsd.org>

check if we were previously on a signal stack before restoring.

OS X fails to restore the old signal stack because the signal stack is
not enabled by default. This causes sigaltstack(2) to fail with

check if we were previously on a signal stack before restoring.

OS X fails to restore the old signal stack because the signal stack is
not enabled by default. This causes sigaltstack(2) to fail with ENOMEM
as ss_size is 0, < MINSIGSTCKSZ.

ok jsing@

show more ...


# a790b3e2 12-Jun-2014 matthew <matthew@openbsd.org>

Add regress test for explicit_bzero.