``follows'' dups, has minimal performance overhead and can ignore certain
binaries (requires /proc).
``follows'' dups, has minimal performance overhead and can ignore certain
binaries (requires /proc).
Like all solutions using 'LD_PRELOAD' it only works with dynamically linked
binaries. Statically linked binaries, for example valgrind, are not supported.
setuid binaries are also not supported ('LD_PRELOAD' disabled for security
reasons).
Like all solutions using 'LD_PRELOAD' it only works with dynamically linked
binaries. Statically linked binaries, for example valgrind, are not supported.
setuid binaries are also not supported ('LD_PRELOAD' disabled for security
reasons).
Most other existing solutions use a second process which colors its input and
pipe stderr to it. However this creates different runtime behaviour resulting
in a different ordering of the output. Partial lines (no newline) also often
Most other existing solutions use a second process which colors its input and
pipe stderr to it. However this creates different runtime behaviour resulting
in a different ordering of the output. Partial lines (no newline) also often
are colored.
- 'COLORED_STDERR_IGNORED_BINARIES'
Comma separated list of binary names/paths which should not be tracked
are colored.
- 'COLORED_STDERR_IGNORED_BINARIES'
Comma separated list of binary names/paths which should not be tracked
but fails to work if the output is colored. See below for an example.
All environment variables starting with 'COLORED_STDERR_PRIVATE_*' are
but fails to work if the output is colored. See below for an example.
All environment variables starting with 'COLORED_STDERR_PRIVATE_*' are
- `{fputc,putc,putchar}_unlocked()` are not hooked with glibc when writing to
stdout (which might be redirected to stderr). Can't be fixed as the compiler
inlines the code into the program without calling any function.
- `{fputc,putc,putchar}_unlocked()` are not hooked with glibc when writing to
stdout (which might be redirected to stderr). Can't be fixed as the compiler
inlines the code into the program without calling any function.
correctly (no inlining), but the test is designed for GNU/Linux.
- 'COLORED_STDERR_IGNORED_BINARIES' requires the `/proc` file system.
Suggestions welcome.
- Output of `strace` is not always colored correctly as the output from
correctly (no inlining), but the test is designed for GNU/Linux.
- 'COLORED_STDERR_IGNORED_BINARIES' requires the `/proc` file system.
Suggestions welcome.
- Output of `strace` is not always colored correctly as the output from