Dear Eric, solaris-pkg-people, bug-m4, This problem was because of missing libssp on my Solaris 10 system.
When I installed libssp0 by the OpenCSW system and applied the following patch to lib/stackvma.c, the problem was fixed. https://www.opencsw.org/packages/libssp0/ https://lists.gnu.org/r/bug-m4/2021-05/msg00020.html https://lists.gnu.org/r/bug-m4/2021-05/txtSlhgMVQhua.txt I am sorry that this m4-build-fail report was not a bug of m4. Best, Hiroshi Hakoyama > 2021/11/08 15:25、箱山洋 <hiroshi-hakoy...@nagano.ac.jp>のメール: > > Dear Eric, > >> Indeed, and yet another reason why I need to make time to release m4 >> 1.4.20 with that fix already included. > Thank you! > >> Can you run this under a debugger to get the stack trace of where the >> error occurs? > Please see below: > > % which gcc > /opt/csw/bin/gcc > > % gcc --version > gcc (GCC) 5.5.0 > Copyright (C) 2015 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > # gcc -Q -v > Reading specs from /opt/csw/lib/gcc/sparc-sun-solaris2.10/5.5.0/specs > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/opt/csw/libexec/gcc/sparc-sun-solaris2.10/5.5.0/lto-wrapper > Target: sparc-sun-solaris2.10 > Configured with: > /home/dam/mgar/pkg/gcc5/trunk/work/solaris10-sparc/build-isa-sparcv8plus/gcc-5.5.0/configure > --prefix=/opt/csw --exec_prefix=/opt/csw --bindir=/opt/csw/bin > --sbindir=/opt/csw/sbin --libexecdir=/opt/csw/libexec > --datadir=/opt/csw/share --sysconfdir=/etc/opt/csw > --sharedstatedir=/opt/csw/share --localstatedir=/var/opt/csw > --libdir=/opt/csw/lib --infodir=/opt/csw/share/info > --includedir=/opt/csw/include --mandir=/opt/csw/share/man > --enable-cloog-backend=isl --enable-java-awt=xlib > --enable-languages=ada,c,c++,fortran,go,java,objc --enable-libada > --enable-libssp --enable-nls --enable-objc-gc --enable-threads=posix > --program-suffix=-5.5 --with-cloog=/opt/csw --with-gmp=/opt/csw > --with-included-gettext --with-ld=/usr/ccs/bin/ld --without-gnu-ld > --with-libiconv-prefix=/opt/csw --with-mpfr=/opt/csw --with-ppl=/opt/csw > --with-system-zlib=/opt/csw --with-as=/usr/ccs/bin/as --without-gnu-as > Thread model: posix > gcc version 5.5.0 (GCC) > > % which gdb > /opt/csw/bin/gdb > > % gdb ./gm4 > GNU gdb (GDB) 7.7 > Copyright (C) 2014 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "sparc-sun-solaris2.10". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from ./gm4...(no debugging symbols found)...done. > (gdb) r > Starting program: /export/home/hako/bin/gm4 > [Thread debugging using libthread_db enabled] > [New Thread 1 (LWP 1)] > *** stack smashing detected ***: terminated > > Program received signal SIGILL, Illegal instruction. > [Switching to Thread 1 (LWP 1)] > fail (msg1=0xff311940 "*** stack smashing detected ***: ", > msg1len=msg1len@entry=33, > msg3=0xff311918 "stack smashing detected: terminated") > at > /home/dam/mgar/pkg/gcc5/trunk/work/solaris10-sparc/build-isa-sparcv8plus/gcc-5.5.0/libssp/ssp.c:169 > 169 > /home/dam/mgar/pkg/gcc5/trunk/work/solaris10-sparc/build-isa-sparcv8plus/gcc-5.5.0/libssp/ssp.c: > No such file or directory. > (gdb) bt > #0 fail (msg1=0xff311940 "*** stack smashing detected ***: ", > msg1len=msg1len@entry=33, > msg3=0xff311918 "stack smashing detected: terminated") > at > /home/dam/mgar/pkg/gcc5/trunk/work/solaris10-sparc/build-isa-sparcv8plus/gcc-5.5.0/libssp/ssp.c:169 > #1 0xff3111fc in __stack_chk_fail () > at > /home/dam/mgar/pkg/gcc5/trunk/work/solaris10-sparc/build-isa-sparcv8plus/gcc-5.5.0/libssp/ssp.c:185 > #2 0x00035970 in sigsegv_get_vma () > #3 0x00035104 in stackoverflow_install_handler () > #4 0x0002afc4 in c_stack_action () > #5 0x0005b568 in main () > (gdb) c > Continuing. > /export/home/hako/bin/gm4: internal error detected; please report this bug to > <bug-m4@gnu.org>: Illegal instruction > [Inferior 1 (process 28630 ) exited with code 02] > > > > Hiroshi Hakoyama > > > > > > > > >> 2021/10/27 22:28、Eric Blake <ebl...@redhat.com>のメール: >> >> On Wed, Oct 27, 2021 at 09:35:37AM +0900, 箱山洋 wrote: >>> Dear m4 developers, >>> >>> I found a bug of m4-1.4.19 on Solaris 10 (SPARC), so I sent a bug report to >>> pkgsrc (http://gnats.netbsd.org/56336). >>> >>> The message says: >>> ./m4: internal error detected; please report this bug to <bug-m4@gnu.org>: >>> Illegal instruction >>> >>> So, I also forward the bug report to bug-m4. >> >> Thanks for the report. >> >>> CC stackvma.o >>> In file included from stackvma.c:1476:0: >>> /usr/include/sys/procfs.h:44:2: error: #error "Cannot use procfs in the >>> large file compilation environment" >>> #error "Cannot use procfs in the large file compilation environment" >>> ^ >>> *** Error code 1 >>> ... >>> >>> This error is similar to the report at >>> https://lists.gnu.org/r/bug-m4/2021-05/msg00020.html >>> https://lists.gnu.org/r/bug-m4/2021-05/txtSlhgMVQhua.txt >> >> Indeed, and yet another reason why I need to make time to release m4 >> 1.4.20 with that fix already included. >> >>> m4 was able to built by this patch, but the execution of m4 showed an error: >>> >>> # ./m4 >>> *** stack smashing detected ***: terminated >>> ./m4: internal error detected; please report this bug to <bug-m4@gnu.org>: >>> Illegal instruction >>> >>> # /usr/pkgsrc/devel/m4/work/.destdir/usr/pkg/bin/gm4 >>> *** stack smashing detected ***: terminated >>> /usr/pkgsrc/devel/m4/work/.destdir/usr/pkg/bin/gm4: internal error >>> detected; please report this bug to <bug-m4@gnu.org>: Illegal instruction >> >> Can you run this under a debugger to get the stack trace of where the >> error occurs? >> >> -- >> Eric Blake, Principal Software Engineer >> Red Hat, Inc. +1-919-301-3266 >> Virtualization: qemu.org | libvirt.org >> >