| Age | Commit message (Collapse) | Author |
|---|
|
For now, this mainly help programs explicitly using
wide-character functions like el_wgetc(3) and el_wgets(3).
1. After reading an invalid byte sequence, do not throw away additional
valid bytes; fix by me using mbrtowc(3), obsoleting utf8_islead().
2. When read(2) returns EOF, return that information to the caller,
do not prod on and potentially access garbage data in the buffer;
from Linas Vepstas via NetBSD read.c rev. 1.70 2013/05/27.
3. After read__fixio() failure, restore errno to the one set by read();
from Steffen Nurpmeso via NetBSD read.c rev. 1.68 2012/09/10.
4. After read__fixio() success, restore errno to the initial state
upon function entry; fix by me.
OK czarkoff@. Also committed to NetBSD.
|
|
|
|
idioms.
Adopt the more concise fcntl(n, F_GETFL) over fcntl(n, F_GETFL, 0)
where it is obvious further investigation will not yield and
even better way.
Obviousness evaluation and ok guenther@
|
|
|
|
Just NULL is not good practise as NULL is theoretically allowed to
be an integer rather than a pointer.
Use (char *)NULL consistently instead of scattering a few (char *)0
and (void *)NULL into the mix.
Prompted by and probably ok deraadt@ millert@ kettenis@
Definitely ok mestre@ ratchov@
|
|
|
|
|
|
|
|
All work done by Martijn Dekker
OK millert@
|
|
enter; issue came up a dir was deleted containing a obj@ link
ok millert
|
|
fixes posix compatibility issue
OK millert@, nicm@, otto@
|
|
suggestion from beck@, OK millert@, otto@
|
|
Should prevent problems if any more debug output is added late in the
connection.
|
|
|
|
Remove machdep.userldt sysctl.
Remove i386_[gs]et_ldt syscall stub from libi386.
Remove i386_[gs]et_ldt regression test.
ok mlarkin@ millert@ guenther@
|
|
that "Bad packet length" errors are 3 lines back instead of the previous
two, which meant we didn't skip some offsets that we intended to.
|
|
chared unit tests now work, so enable them.
|
|
A few tests are enabled and work, so this starts being useful.
|
|
Those that still fail are commented out in the Makefiles for now;
i have patches for them.
|
|
openssl md5 adds a "(stdin)= " prefix to the output, but all we need is
the actual md5 sum itself. This caused most of the ffs regress tests to
fail.
ok mpi@
|
|
|
|
misbehaviour is triggered with 'c' and 'i' commands on empty buffers.
Spotted and fixed by Martin Natano <natano at natano dot net>.
ok millert@
|
|
$SUBDIRS so do it explicitly
|
|
|
|
|
|
fiddling with the internals of that code is dangerous without it.
Intentionally not linked to the build yet, because many of the tests
still fail: The related bugfixes are too intrusive right now and will
go in after unlock.
|
|
|
|
|
|
output from man -f: Messages "man: nothing appropriate" are not helpful.
If no matching manual exists anywhere, a more specific message follows
right afterwards. If a matching manual exists in the current directory,
such messages are just wrong.
Issue reported by jmc@.
|
|
removed 2 years ago) by a (working) test for @ask-update
|
|
|
|
the emacs editing mode code, so add a testsuite before touching it.
To avoid having to deal with the horrendous low-level terminal
handling and high-level command execution code, write the tests in
unit test style rather than in integration test style, by providing
minimal glue to run vi.c stand-alone. In case relevant internal
interfaces in sh.c, edit.c, and friends are changed, the glue may
need adjustment.
Not testing completion and history at this time, only line editing.
|
|
|
|
both in the same way as it was done for ul(1).
No functional change.
|
|
|
|
The current code has already setted it by default since 1.74
any pledge failure tries to make a coredump (default rules for coredump still
applies: so setuid binaries don't create them locally).
ok deraadt@
|
|
message is logged to the console by the kernel.
|
|
Even though this is testing UTF-8, the test file is 7-bit clean.
Will be enabled once the ul(1) program is fixed.
|
|
file. All subtests get an additional /dev/console entry in
syslog.conf, then check that messages appear in the console file.
Add a test that stops syslogd, calls sendsyslog2() with LOG_CONS
and checks that the message appears in the console file.
|
|
ok beck@
|
|
That should make it easier for others to set up the test.
|
|
tabs, backspaces, multibyte characters of width 1, 0, and 2,
invalid bytes and non-printable characters. All tests are run
both with the UTF-8 and the C locale.
About half the tests are currently broken, and not only the multibyte
tests, but also half of the tab and backspace tests. The program is
expected to be fixed soon, and the suite will be hooked up after that.
|
|
explain why they are expected.
|
|
report.
|
|
|
|
|
|
|
|
|
|
|
|
|
