-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [please don't top-post]
According to Thomas J. Duck on 12/3/2008 7:29 PM: > Hi Eric, > > Thanks for your email -- the quickest response to a bug report ever! > > 'locate libsigsegv' turns up nothing. It doesn't turn up anything for me, either, because it is not an executable, but a library. More to the point, you can find out if m4 is using libsigsegv by inspecting your config.log output. For example, when I built a recent development copy of m4, my config.log contains: configure:7054: checking for libsigsegv configure:7082: result: yes configure:7088: checking how to link with libsigsegv configure:7090: result: -lsigsegv and further searching turns up /usr/include/sigsegv.h which includes: #define LIBSIGSEGV_VERSION 0x0204 /* version number: (major<<8) + minor */ so my machine has libsigsegv 2.4 installed (no known bugs when used on cygwin, but according to the NEWS file, this version is buggy on at least Mac, BSD, and Linux; 2.6 is the most recent release, but even that still has bugs on fringe platforms like Irix that are only fixed in CVS libsigsegv). > > If you have other tests that you would like me to run, please let > me know. I'm happy to help where I can. Are you comfortable using gdb (assuming you have that installed)? Are you able to figure out how to run the failing test under gdb such that you can give a stack trace at the point where the SIGBUS occurred, or would you like a step-by-step walkthrough? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk3SO0ACgkQ84KuGfSFAYCx2ACeJ0qnSiRu4N3xMI5p79iog4Wa KuAAn03GZ11VTmxFOlAZlDpbQveOGdQZ =baiT -----END PGP SIGNATURE-----
