<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/regress/lib/libc/explicit_bzero, branch libressl-v3.1.2</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v3.1.2</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v3.1.2'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2014-07-11T01:10:35+00:00</updated>
<entry>
<title>Fix dumb copy/paste mistake.</title>
<updated>2014-07-11T01:10:35+00:00</updated>
<author>
<name>matthew</name>
<email></email>
</author>
<published>2014-07-11T01:10:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7c1604ababbfbcde0bc72c482acfe72d9c10b77d'/>
<id>urn:sha1:7c1604ababbfbcde0bc72c482acfe72d9c10b77d</id>
<content type='text'>
Noticed testing with clang.
</content>
</entry>
<entry>
<title>Fix explicit_bzero regress for Solaris and OS X compatibility</title>
<updated>2014-07-11T00:38:17+00:00</updated>
<author>
<name>matthew</name>
<email></email>
</author>
<published>2014-07-11T00:38:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=11fac66b3ab86680074b2fba3298980b044d27f7'/>
<id>urn:sha1:11fac66b3ab86680074b2fba3298980b044d27f7</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Add some extra sanity checks to make sure the test functions actually</title>
<updated>2014-07-09T23:54:00+00:00</updated>
<author>
<name>matthew</name>
<email></email>
</author>
<published>2014-07-09T23:54:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=cff606a33656a8e3011d25140ec13caa6318498a'/>
<id>urn:sha1:cff606a33656a8e3011d25140ec13caa6318498a</id>
<content type='text'>
run on altstack.
</content>
</entry>
<entry>
<title>Better workaround for OS X sigaltstack() bug</title>
<updated>2014-07-09T18:02:24+00:00</updated>
<author>
<name>matthew</name>
<email></email>
</author>
<published>2014-07-09T18:02:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=790a05b5b877aef073b28191afbe8846ce04a9d3'/>
<id>urn:sha1:790a05b5b877aef073b28191afbe8846ce04a9d3</id>
<content type='text'>
OS X's sigaltstack() fails with ENOMEM if ss_size &lt; 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.
</content>
</entry>
<entry>
<title>check if we were previously on a signal stack before restoring.</title>
<updated>2014-07-09T14:26:59+00:00</updated>
<author>
<name>bcook</name>
<email></email>
</author>
<published>2014-07-09T14:26:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=4dd79c01d19267f9e0e25c16ef93a63aeca9d177'/>
<id>urn:sha1:4dd79c01d19267f9e0e25c16ef93a63aeca9d177</id>
<content type='text'>
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, &lt; MINSIGSTCKSZ.

ok jsing@
</content>
</entry>
<entry>
<title>Add regress test for explicit_bzero.</title>
<updated>2014-06-12T22:01:55+00:00</updated>
<author>
<name>matthew</name>
<email></email>
</author>
<published>2014-06-12T22:01:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=8691a763686f761c05088245e7103f86d01fcabb'/>
<id>urn:sha1:8691a763686f761c05088245e7103f86d01fcabb</id>
<content type='text'>
</content>
</entry>
</feed>
