On Tue, Sep 03, 2013 at 02:36:13PM +0300, Vitalij Satanivskij wrote: > > Hello. > > On fresh installed system - > > 10.0-CURRENT FreeBSD 10.0-CURRENT #3 r255173: Tue Sep 3 13:31:22 EEST 2013 > > With fresh i386 builded jail. I'm found some bug with core dumped uniq (/usr/bin/uniq) > > After recompile whole system with debug symbols found some trace > > gdb /usr/bin/uniq uniq-1676.core > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 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 "i386-marcel-freebsd"... > Core was generated by `uniq'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /lib/libc.so.7...done. > Loaded symbols for /lib/libc.so.7 > Reading symbols from /libexec/ld-elf.so.1...done. > Loaded symbols for /libexec/ld-elf.so.1 > #0 0x00000001 in ?? () > (gdb) bt > #0 0x00000001 in ?? () > #1 0x281a1e94 in __default_hash () from /lib/libc.so.7 > #2 0xffffcba8 in ?? () > #3 0x28153361 in verrc (eval=<value optimized out>, fmt=<value optimized out>, ap=<value optimized out>) at /usr/src/lib/libc/gen/err.c:112 > Previous frame identical to this frame (corrupt stack?) > (gdb) > > > I's any change to fix problem ? Your installed libraries do not have proper debugging symbols. Since the issue seems to be in the compat32 layer, you may try to start with taking the ktrace of the failing program and see what syscall failed, if any.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:41 UTC