Skip to content

Releases: flonatel/pipexec

Fixed rare by-one buffer overflow; Improvements

16 Oct 14:41
Compare
Choose a tag to compare
  • Fixes by-one buffer overflow in rare cases: When logging is enabled and at position 4096 a comma needs to be written, then there was an buffer overwrite by one.
  • Upgraded CodeQL check to new version.
  • Upgraded Compile check to new version and added the following
    compilers:
    • gcc: 12, 13, 14 (using Ubuntu 24.04)
    • clang: 16, 17, 18 (using Ubuntu 24.04)

Fix 32 bit build

20 Jun 20:24
Compare
Choose a tag to compare
  • Fixes 32 bit build
    On 32 bit platforms size_t is not unsigned long. Fixes size_t output.

Add JSON logging; Improvements and Fixes

20 Jun 08:45
Compare
Choose a tag to compare
  • Check for duplicate pipe definition
    pipe endpoints can only be used once. If two times the same source or sink were specified in the command line, the behavior was (and still is) undefined.
    Now a check was added that emits a error log, if a pipe endpoint is specified twice.
  • Added json logging
    Using the -j option pipexec now logs in json format that can be parsed. This provides information about status and exit codes of child processes.
  • Exit with 1 when one child fails
    When at least one child fails, pipexec also fails with '1'.
  • Check for rubbish on the command line
    Additional or unparsable command line arguments are now seen as an error. Before there were silently ignored.
  • Fixed false positive dangling pointer check of gcc 12
    GCC introduces a new dangling pointer check which runs into a false positive.
  • Add compile check for wide range of compilers
    As public travis access was switched off some time, pipexec now uses github CI/CD for compile check. The following compilers are checked:
    • gcc: 9, 10, 11, 12
    • clang: 10, 11, 12, 13, 14

Fixes minimal buffer usage in peet & Fixes version string in usage text

28 Aug 20:32
Compare
Choose a tag to compare

Previous versions of 'peet' only use 8 bytes read buffer - due to a programming bug. This does not do any harm - except that it might be a performance issue. (Closes #8).
All binaries now print out the correct version string:

  • when build from the tar ball the version of the tar ball is used.
  • when build from a git clone, the version has a format like 'pipexec version 2.5.4-11-g7161b102'
    This closes #5.

Fixes configure environment

25 Jul 18:29
Compare
Choose a tag to compare

Due to an irritation some files were not included in the 2.5.3 tarball (even if the building script was the same as for all old versions.)
This releases fixes this: it re-adds all the needed scripts for / from autmake / autoconf.

Fixes Bug#790272: pipexec: FTBFS with glibc 2.21 and gcc-5

21 Jul 09:33
Compare
Choose a tag to compare

*** Do not use this release - it cannot be build directly from the tar ball, because of a packing problem. Please use the current version ***

Starting with libc6-21 the _BSD_SOURCE is marked as deprecated - and a warning is emitted. Because pipexec is compiled with -Werror it does not compile any more.
Instead of using _BSD_SOURCE pipexec now uses _DEFAULT_SOURCE.
(Tested under Debian Jessie, Debian Stretch, and Debian experimental with libc6-21 and gcc-4.9.3 and gcc-5.2.1).

Fixed Man Page Lincense

29 Mar 08:00
Compare
Choose a tag to compare

In man pages there was a hint to (only) GPL2 and not GPL2+. This was fixed now.

Fixed Man Page

27 Mar 06:45
Compare
Choose a tag to compare

There were some problems with the man page which are fixed in this release.

Prepare for Debian / Man pages

17 Mar 11:42
Compare
Choose a tag to compare

Only small infrastructure changes:
o added man pages
o removed debian directory
o add script for packaging

Signal handling improvements

19 Jul 05:32
Compare
Choose a tag to compare

pipexec now comes with some improvements of signal handling.