-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Mark Hobley on 12/30/2009 1:03 AM: >> You'll have to demonstrate an instance of the bug in >> context, first. > > I'm trying. I need some faulty code that consistently trips the logger. I don't know what causes this yet, but I have seen it trip. Unfortunately because the logger was broken, the script bombed out and I have not located the cause of the trip. Can you enable shell tracing, or even a debug echo statement at the top of as_fn_error, in order to sniff out if someone is ever invoking that function with incorrect arguments? - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----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/ iEYEARECAAYFAks7Ta4ACgkQ84KuGfSFAYC0uwCfSvmF0y2uPEaN/qk7mcYH7U+S JM4AnAsjpZwGuRH7T0h1OAzDP0aBrgE4 =VxqE -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
