| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
Patches provided by Joel Baker in PR 22365, verified by myself.
|
|
|
|
it does and to better signal it might modify it's arguments
fixes PR bin/20546 by Peter Seebach
|
|
|
|
remove ()'s from error messages
move some error checks immediatelly after appropriate realloc() calls
|
|
for correct formatting of the SYNOPSIS any longer.
|
|
difficult to read and understand. Most manuals of English style
therefore say that you should use "use".
|
|
|
|
cosmetic change to how local variable is incremented (moved to for(;;))
|
|
|
|
use fseeko() rather than fseek() when changing file offset using max_o
|
|
de-__P()
|
|
|
|
want to be able to open as many temporary files as possible
|
|
this fixes second part ('tmpdir get smashed') of bin/18614 by Michael Graff
|
|
definitions in init.c and field.c
g/c MAXMERGE
|
|
g/c superfluous extern definition for clist[] and ncols
make toutpath[] static
|
|
|
|
such usage is broken. Problem pointed out by Klaus Klein on
"sources-changes@netbsd.org".
|
|
build problem after siginfo(2) has been added.
|
|
|
|
|
|
|
|
foo += sscanf(++foo, ...);
constructs to:
++foo;
foo += sscanf(foo, ...);
to avoid the following warning from gcc 3.1:
warning: operation on `pos' may be undefined
|
|
|
|
actually read already. Albeit it's not damaging to copy zero data
for bufend == crec->data case, the buffer end could also be between
memory position 'crec' and 'crec->data'. Thus, we could end up with
negative 'bufend - crec->data' value, and obvious havoc.
This change fixes lib/12673, though the problem was masked and no longer
repeatable with the provided example after the recent buffer size bump.
The change was tested with the buffer size change backed off, and really
fixes the problem in the PR.
|
|
free keylist, buffer on end of work; no functional changes
|
|
|
|
needed now
|
|
if needed and record count is within bounds (<MAXNUM), rather than
sorting the input by 64KB chunks. This cuts the number of needed
temporary files considerably (and improves performance, too).
Slighly adjust some #defines, mostly to power of 2 values.
This addresses bin/12673 and bin/12614, as well as complains from other
people.
|
|
For some reason this program wants to open _hundreds_ of temporary files.
Make it setrlimit(RLIMIT_NOFILE, ...), so this rather dubious strategy at
least works well enough to ctag(1) our own kernel.
XXX
|
|
|
|
This change tracks change in rev 1.25 of sort.c by Christos Zoulas.
While here, improve error messages slighly.
|
|
path buffer
- provide better error messages about why the temp file creation is failing
- explicitly compare syscall return to -1 instead of < 0 and fdopen return
to NULL instead of 0.
|
|
If no output file was specified sort fopened("/dev/stdout", "w").
This is *wrong* because "/dev/stdout" will truncate the output file,
thus undoing the append effect the shell had set up. The simple fix
here is to just arrange for outfp = stdout and don't play with /dev/stdout.
While I am here:
- KNF
- make pattern for mkstemp have 6 X's.
|
|
This fixes the 'sort -f /dev/null' coredump reported on current-users.
|
|
whitespace changes, which don't influence the layout of result manpage at all,
but also add -H to SYNOPSIS and state sort(1) appeared in v5, not v6 of
AT&T Unix.
|
|
This is primarily to ease syncing the two versions.
|
|
branch, since we might get called with tablepos == endkey for some special
input files (where an record would happen to fit exactly to the input
buffer) - BTW, this bug looks like it has been here ~forever ...
This seems to fix the sort crash for 'make british' build of ispell package,
as reported by Mark White at current-users@.
|
|
* move the test for keybuf size before keypos[-1] assignment, "just in case"
* move the keypos assignment to improve readability
|
|
|
|
* move the test for keybuf size before keypos[-1] assignment, "just in case"
* move the keypos assignment to improve readability
|
|
in fsort.h, move macro SALIGN() from sort.h to fsort.c
|
|
|
|
resurrect ENVIRONMENT and FILES, adjust to be more correct
slighly adjust SYNOPSIS line, so that it looks little nicer :)
|
|
|