In an ancient message, Jack Gundrum wrote:
> Hi,
> I get the following from both m4 1.4 and m4 1.4o on my Ultra60 running
> Solaris 2.7. I need m4 to make autoconf only. Any ideas/help appreciated.
>
>
> spork% m4 --version
> GNU m4 1.4o
> Memory bounds violation detected (SIGSEGV). Either a stack overflow
> occurred, or there is a bug in m4. Check for possible infinite recursion.
> Segmentation Fault (core dumped)
> spork%
Recompile with debugging, and have a look at the core dump with gdb. If you
don't know how to do that try the following, and send a copy of the output
back here:
$ make clean
$ make CFLAGS=-g
$ ./src/m4 --version
[assuming you still get the core dump:]
$ gdb ./src/m4 core
gdb> backtrace
For what its worth, I have m4-1.4 working on Solaris 2.5, 2.5.1, 2.6 and 2.8,
and I have m4-1.4p working on Solaris 2.8... all without any problems or
peculiarities.
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(oranda.demon.co.uk|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk ,_())____
/ )= GNU Hacker http://www.gnu.org/software/libtool \' `&
`(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/
_______________________________________________
Bug-m4 mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-m4
