Re: m4 1.4.18 fails immediately when run on Mac

[Eric Blake]

On 11/22/19 12:59 PM, Vanessa McHale wrote:
> Hi all,
>
> When I try to run m4 on my Mac, it immediately fails with
>
> Abort trap: 6

Can you get a backtrace of where the abort() call is happening?  I don't 
have access to a Mac, so I am not in a position to easily reproduce the 
failure.

> I built using the traditional ./configure ; make -j8 and then run it with
>
> ./src/m4

Since you are building from source, you may also want to try modifying 
main() to not install a signal handler for SIGABRT; that way, the 
desired abort message will get printed rather than m4's normal attempt 
to sanitize a fatal error into a more friendly message.

> This is the result of gcc --version:
>
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
> --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
> Apple clang version 11.0.0 (clang-1100.0.33.12)
> Target: x86_64-apple-darwin19.0.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>
> Thanks!
> Vanessa McHale

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org