On Thu, Oct 26, 2006 at 03:25:17PM +0000, [EMAIL PROTECTED] wrote: > > Given the involvement of ld-linux.so.2, I tried building and using a > statically linked bash (3.2), and sure enough it does NOT exhibit the > segfaults at all. >
It seems I was a bit premature here. The static bash does indeed segfault with the same symptoms: GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc64-unknown-linux-gnu". (gdb) file /bin/sh Reading symbols from /bin/sh...(no debugging symbols found)...done. Using host libthread_db library "/pkg/glibc/lib/libthread_db.so.1". (gdb) core-file /tmp/corefiles/core Core was generated by bin/sh /home/public/sparc64/tmp/gcc-4-1.heretix/gcc-4.1.1/libiberty/configure'. Program terminated with signal 11, Segmentation fault. #0 0x0000000000196a90 in siglongjmp () (gdb) bt #0 0x0000000000196a90 in siglongjmp () #1 0x0000000000205cac in _dl_signal_error () (gdb) > > Andrew Walrond _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
