Open dancek opened 6 years ago
Turns out this is a bug in coreutils' vasnprintf. Sorry for reporting in the wrong place. I'm sending a PR of a patched build soon; expect a working version of lbzip2 in Homebrew in a week.
The issue is in gnulib (rather than coreutils as I previously stated) and I only now realize that lbzip2 in fact ships a copy of gnulib in its tarball. Basically a new release with a fixed version of gnulib is needed to make the crash on macOS 10.13 go away.
The relevant gnulib mailing list thread: http://lists.gnu.org/archive/html/bug-gnulib/2017-07/msg00056.html
I'd make a PR but since lib/
doesn't exist in the git repo there's nothing to edit.
In order to work around Issue #22, I have published my own source distribution for lbzip2 2.5 which is bootstrapped using the latest version of gnulib. See my comment on that issue for further details. The distribution probably also works around this issue, though as I don't have macOS I can't check.
MacPorts users are experiencing this problem too. Can you please fix it by releasing a new version, with a source tarball built using the fixed version of gnulib?
@ryandesign: See my previous comment for a workaround. If you are responsible for the MacPorts package, then you could temporarily switch to my fork.
Again: Can you please fix it by releasing a new version, with a source tarball built using the fixed version of gnulib?
Using the parameter
-v
causes lbzip2 to crash for me. Weirdly after that happens, any call to lbzip2 crashes for a while. After a few minutes (and doing something else) it works again.This is on lbzip2 2.5 installed from Homebrew. It's built with
./configure --disable-debug --disable-dependency-tracking
in case that matters.Here's the crash log: