summaryrefslogtreecommitdiff
path: root/src/regress/lib/libc (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Change gmtime() to return time in UTC rather than GMT, as required by our ownphessler2 days1-79/+79
| | | | | | manpage, POSIX, C standards, and other OSes. OK kettenis@, millert@
* Add missing make dependency as the oclo binary depends onanton10 days1-1/+3
| | | | | ocloexec_verify. Take the easy route and ensure all binaries are built before the regress make target.
* link illumos oclo test to the treetb2025-08-041-2/+2
|
* Provide harness to run illumos's oclo tests from libc regresstb2025-08-023-0/+32
| | | | | | | This depends on the illumos-os-tests port I just imported and can be linked to the build once guenther lands the close-on-fork diff. Adapted from an initial diff by Ricardo Branco
* hash_test: remove variable name from prototype and fix a casttb2025-08-021-3/+3
|
* Add a test to verify the fpurge problem doesn't happen. fpurge()yasuoka2025-06-121-1/+41
| | | | | mistaknely made the write buffer usable even if the stream is read mode. See the change of lib/libc/stdio/fpurge.c,v 1.11.
* Test to verify the handling of fflush() for the pushed-back buffer thatyasuoka2025-06-081-1/+40
| | | | has been read or that has not.
* Now our fflush() comply POSIX-2008. test_fflush is expected "pass".yasuoka2025-06-032-6/+3
| | | | And switch test___freadahead to use another version that uses fflush().
* explicit_bzero test: don't redefine __SANITIZE_ADDRESS__tb2025-05-311-1/+3
| | | | Silences an annoying warning when running tests with ASAN.
* Add test whether fflush() complies POSIX for the handling ofyasuoka2025-05-251-1/+82
| | | | pushed-back wchar_t chars.
* Add test for ungetwc().yasuoka2025-05-252-1/+94
|
* Add tests for the functions in <stdio_ext.h>.yasuoka2025-05-257-2/+455
|
* Include "stdio" in SUBDIR. This should have been done along with theyasuoka2025-05-251-4/+4
| | | | previous commit.
* Add regress/lib/libc/stdio/test_fflush.c to test fflush() behavior foryasuoka2025-05-242-0/+236
| | | | | | reading FILE objects. It will fail until fflush() complies POSIX-2008. ok tb asou
* Adapt to new maloc_options declarationotto2025-05-241-2/+2
|
* Adapt test to new malloc_options regimeotto2025-05-241-7/+8
|
* Enable remaining tests with NULL, 0tb2025-04-142-9/+3
| | | | Now that libc is fixed, we can do this also for md5, rmd160 and sha1.
* Link hash regress to buildtb2025-04-141-1/+2
|
* Add some regress coverage for the hashes in libctb2025-04-142-0/+946
| | | | Prompted by a pending diff by claudio
* Avoid compiler warning on some OStb2025-04-131-1/+1
| | | | | | | | Some OS declare arc4random() with __attribute__((warn_unused_result)) causing this test to whine. So explicitly ignore the return value. Reported by scheiba in libressl/portable Fixes #1151
* t_recvmmsg and t_sendmmsg were enabled in 2022guenther2024-08-151-2/+0
|
* sched_yield() is not strong enough to overflow the recv buffer on someclaudio2024-07-301-2/+2
| | | | systems. Use a proper sleep using usleep(100) instead.
* fix signature of main()anton2024-07-151-4/+3
|
* enable warnings and apply a dash of knfmtanton2024-07-152-1/+2
|
* Add elf_aux_info(3)jca2024-07-143-1/+59
| | | | | | | | Designed to let userland peek at AT_HWCAP and AT_HWCAP2 using an already existing interface coming from FreeBSD. Headers bits were snatched from there. Input & ok kettenis@ libc bump and sets sync will follow soon
* t22 and t23 can fail if the first chunk ends up being allocated atotto2024-04-141-2/+12
| | | | | the very end of the page. Circumvent that. Reported by and fix ok anton@
* Ugly workaround to let this compile again on non-clang platforms.miod2024-03-051-1/+9
|
* Cope with recent ctype.h prefix changes.anton2024-02-051-5/+5
|
* More missing voidtb2024-02-041-3/+3
| | | | From Christian Andersen
* Remove 3 expected failures those got fixed in the regress code.claudio2023-10-311-4/+1
|
* unlink("/") just needs to error. Checking for a specific errno makesclaudio2023-10-311-2/+2
| | | | | | little sense here since there are multiple possible errnos that could be returned. On OpenBSD this returns EISDIR and not EBUSY. OK mbuhl@ millert@
* When creating a file in a directory the file gid is inherited fromclaudio2023-10-311-2/+2
| | | | | the directory and so checking against getgid() makes no sense. OK mbuhl@ millert@
* Ignore closefrom() failure. This fails normally since fd 4 and up are allclaudio2023-10-311-3/+2
| | | | | closed. OK mbuhl@ millert@
* Include wait(2) status in error message, in the hopes of providing cluesanton2023-10-271-2/+2
| | | | on why this occasionally fails.
* A few more testsotto2023-10-221-1/+15
|
* We're not interested in the core dump, so prevent it. Also catchotto2023-09-271-3/+17
| | | | | SIGABRT, to avoid the "Abort trap" message, which confuses me sometimes until I realize it's the purpose of this test to abort.
* Extent the modf() tests; from Willemijn Coene.miod2023-08-131-18/+50
|
* add regress tests for the remainder of the function provided by our uuid.hjasper2023-07-031-5/+137
|
* More thorough write-afetr-free checks.otto2023-06-041-6/+21
| | | | | | | | | | | | | | | | | | | On free, chunks (the pieces of a pages used for smaller allocations) are junked and then validated after they leave the delayed free list. So after free, a chunk always contains junk bytes. This means that if we start with the right contents for a new page of chunks, we can *validate* instead of *write* junk bytes when (re)-using a chunk. With this, we can detect write-after-free when a chunk is recycled, not justy when a chunk is in the delayed free list. We do a little bit more work on initial allocation of a page of chunks and when re-using (as we validate now even on junk level 1). Also: some extra consistency checks for recallocaray(3) and fixes in error messages to make them more consistent, with man page bits. Plus regress additions.
* Make malloc tests that set flags more robust against the user alsootto2023-05-092-15/+19
| | | | having flags set.
* Enable malloc_errs testotto2023-05-081-2/+2
|
* Add a regress test to test various malloc API and heap mismanagementotto2023-05-082-0/+291
| | | | | errors which should cause abort. A few are not enabled yet, they will be once the corresponding diffs in malloc are committed.
* remove duplicate includesjsg2023-04-191-2/+1
|
* Fix compilation on sparc64.mbuhl2023-04-131-2/+3
|
* WTRAPPED is now supported by waitid(2)guenther2022-12-191-3/+3
| | | | | Don't test waitid(WUNTRACED) as that's not portable and only 'works' due to an implementation decision
* userspace: remove vestigial '?' cases from top-level getopt(3) loopscheloha2022-12-042-4/+2
| | | | | | | | | | | | | getopt(3) returns '?' when it encounters a flag not present in the in the optstring or if a flag is missing its option argument. We can handle this case with the "default" failure case with no loss of legibility. Hence, remove all the redundant "case '?':" lines. Prompted by dlg@. With help from dlg@ and millert@. Link: https://marc.info/?l=openbsd-tech&m=167011979726449&w=2 ok naddy@ millert@ dlg@
* simplify makefileanton2022-11-221-8/+2
|
* Be more helpful and provide details on what the time conversion testsanton2022-11-221-9/+6
| | | | | | need in order to run. Also, output the expected SKIPPED string as dictated by bsd.regress.mk.
* Use /tmp as opposed of /var/tmp as the default directory for temporaryanton2022-11-101-2/+2
| | | | files.
* Add tests for boundary conditions of struct tm.beck2022-11-091-1/+125
| | | | Struct tm is limited by it's year being an int.