| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
- Removed dead declarations
- Made objects that should have been declared as static, static.
The changes use STATIC instead of static, following the existing
convention in the rest of the code.
Approved by: schweikh (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
output buffer, don't insert them at all. This prevents a buffer
*underrun* when the substitution consists completely of newlines
(e.g. `echo`) and the byte before the source buffer to which p
points is a '\n', in which case more characters would be removed
from the output buffer than were inserted.
This fixes certain port builds on sparc64.
Approved by: re (scottl)
Reviewed by: des, tjr
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
Submitted by: Tim Kientzle <kientzle@acm.org> (embellished by me)
|
|
|
|
|
|
| |
Due to the use of signed vs. unsigned chars on our various platforms, one gets
"warning: comparison is always true due to limited range of data type"
from GCC 3.3.
|
| |
|
|
|
|
|
| |
PR: docs/51480 (only a small part)
Submitted by: Diomidis D. Spinellis <dds@aueb.gr>
|
|
|
|
|
|
| |
mutually exclusive. The fact that the most recent one specified on the
command line is the one that takes effect is an implementation detail and
users should not rely on this.
|
|
|
|
|
|
|
| |
the child process writing data that the parent should have written.
PR: 50051
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial stack_block is staticly allocated and will be aligned
according to the alignment requirements of pointers, which does not
necessarily match the alignment enforced by ALIGN. To solve this a
more involved change is required: remove the static initial stack
and deal with an initial condition of not having a stack at all. This
change is therefore more risky than the previous ones, but unavoidable
(other than not using the platform default alignment).
Discussed with: tjr
Approved and reviewed by: tjr
Tested on: alpha, i386, ia64 and sparc64
|
|
|
|
| |
why this is breaking sparc64.
|
|
|
|
|
|
| |
The problem with the previous attempt, as noticed by Marcel, was that
stacknxt was being aligned to a pointer boundary instead of an
ALIGNBYTES + 1 boundary, which broke sparc64.
|
|
|
|
|
|
| |
using the alignment from sys/param.h (16) instead of the alignment
from machdep.h (8) tickled a nasty bug in the memory allocator that I
haven't been able to track down yet.
|
|
|
|
| |
incorrect version in machdep.h. Delete machdep.h.
|
| |
|
|
|
|
|
| |
modifiers. The paragraph that explains the difference between ${foo:-bar}
and ${foo-bar} etc. was not very visible.
|
|
|
|
|
|
|
| |
it doesn't interfere with the user's redirections.
PR: 47136
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
from the Makefile:
- Print pointers with %p instead of %x.
- Include missing headers to get prototypes.
Noticed by: benno
|
|
|
|
|
|
|
|
| |
expari(), expbackq() and evalvar(). Similar to revision 1.39.
Patch from Tor Egge.
PR: 45349
MFC after: 2 weeks
|
|
|
|
| |
the POSIX wordexp() function.
|
| |
|
| |
|
|
|
|
|
|
| |
PR: 46015
Submitted by: Jeroen Ruigrok van der Werven <asmodai@wxs.nl>
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
manual page to reflect the code.
PR: 45820
Submitted by: Marco Molteni <molter@tin.it>
Discussed with: tjr
|
| |
|
|
|
|
| |
status of a background process that has terminated because of a signal.
|
|
|
|
| |
Approved by: re
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
|
|
|
|
|
|
|
| |
are later stripped with rmescapes() in expandarg(). If the filename has
already been unescaped, doing it again in rmescapes() can walk off the
end of the string, leading to memory corruption and eventually SIGSEGV.
Noticed by: kris
|
|
|
|
|
|
| |
commands. Commands like "if then ... fi" and "while do ... done" are no
longer accepted. Bodies of compound commands are still allowed to be
empty, because even though POSIX does not allow them, most shells do.
|
|
|
|
|
| |
using %td when we know that the number is between 0 and 9; mksyntax is a
build tool and needs to work on -stable.
|
|
|
|
| |
in the previous commit.
|
|
|
|
|
| |
libc's vfprintf() that writes to a `struct output' instead of a file.
Inspired by NetBSD's similar changes (they used asprintf() instead).
|
|
|
|
| |
Tested on: alpha, i386, sparc64
|
|
|
|
|
|
| |
a program fails because the file or a path component does not exist.
Suggested by: bde
|
|
|
|
|
|
|
|
| |
- Cast rlim_t to intmax_t when printing it.
This should fix the last format errors in sh(1).
Tested on: i386, sparc64
|
|
|
|
| |
errors with %qd formats.
|
|
|
|
|
|
|
|
|
|
|
| |
pointers. This fixes two format warnings on 64 bits
archs which are fatal now that WFORMAT=0 has been removed.
It doesn't fully fix the sh(1) build on 64 bits platforms
though, there is still some quad_t issues that need to be
fixed.
Tested on: i386, sparc64
|
|
|
|
|
| |
on at least i386. If there are warnings on other archs, I'd rather hear
about them than pretend they didn't exist.
|
|
|
|
| |
function in libc.
|
|
|
|
|
|
| |
adding history and vi/emacs-style line editing to the shell itself.
Atty was a user-mode terminal emulator (like screen and window) that did
line editing and history.
|
|
|
|
| |
error message. Stops ulimit giving error messages like "ulimit: ulimit: xyz".
|
|
|
|
| |
us to accept this, but I've never seen a script that uses it.
|
|
|
|
|
|
|
| |
of autoconf are generating scripts that use this feature.
PR: 43275 35879
Submitted by: Dan Nelson <dnelson@allantgroup.com>
|
| |
|
|
|
|
| |
errmsg() and its table of error messages.
|
|
|
|
| |
no-op. I assume it was meant that the close-on-exec flag be set here.
|
|
|
|
| |
Reviewed by: tjr
|