Re: do not get any output using debug options...

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[please don't top-post, and dropping m4-discuss from cc]

According to Tovrea, George W (US SSA) on 8/12/2009 7:12 AM:
>> I do not get any output when running with any combination of -d, -o
>> file, --debug, --debug=aeq, --debugfile=file
>
> System:
> 
> SunOS siamese 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Blade-1500

Hmm.  m4 1.4.13 works for me on the Solaris 10 machine that I have access to.

> Make check:

Looks good - all tests passed.

So, can you give more details, like an actual command line that is doing
the wrong thing for you?  Until I can reproduce this, I'm not sure why
things are acting up for you.

> 
> How do I know if I am using libsigsegv? I did not use any of the sigsegv
> options when configuring M4.

You aren't using it.  But Solaris 10 doesn't need to use libsigsegv (it is
one of the few platforms that already complies with POSIX when it comes to
detecting stack overflow; not even Linux can claim that).

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----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/

iEYEARECAAYFAkqCwPkACgkQ84KuGfSFAYA23ACgzfWFkQrX+GCtYbwfRlrBa9pS
XIUAoIAEYOMtZkY3vWK3E+lMyHEIkiFj
=yJIK
-----END PGP SIGNATURE-----