[Buildroot] ssh-keygen seg fault

[Kyle Hayes]

Hi Thomas,

See below...

On Fri, Jan 14, 2011 at 9:19 AM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Yes, it's definitely something wrong in the build process, and it'd be
> great to sort it out.
>
> Would you mind running ssh-keygen under gdbserver+cross-gdb as
> suggested in my first e-mail ? Or run "ulimit -c unlimited" on your
> board, get ssh-keygen to crash, and then transfer the core file to your
> development workstation, and get a backstrace with the cross-gdb. That
> would immediatly point us to the segfault location, which would really,
> really help in understanding what the issue is.

I got a core file.  I have a target GDB for use with host programs.  I
turned off stripping.  But...

sudo /home/kyle/buildroot/buildroot/output/toolchain/gdbhost-7.1/gdb/gdb
/home/kyle/buildroot/buildroot/output/target/usr/bin/ssh-keygen
/media/HC/core
GNU gdb (GDB) 7.1
Copyright (C) 2010 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 "--host=i686-pc-linux-gnu
--target=i486-unknown-linux-uclibc".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/usr/bin/ssh-keygen...(no
debugging symbols found)...done.
[New Thread 549]

warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the
expected address (wrong library or version mismatch?)
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/usr/lib/libcrypto.so.1.0.0...done.
Loaded symbols for
/home/kyle/buildroot/buildroot/output/target/usr/lib/libcrypto.so.1.0.0
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/lib/libdl.so.0...(no
debugging symbols found)...done.
Loaded symbols for /home/kyle/buildroot/buildroot/output/target/lib/libdl.so.0
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/lib/libutil.so.0...(no
debugging symbols found)...done.
Loaded symbols for /home/kyle/buildroot/buildroot/output/target/lib/libutil.so.0
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/usr/lib/libz.so.1...done.
Loaded symbols for
/home/kyle/buildroot/buildroot/output/target/usr/lib/libz.so.1
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/lib/libcrypt.so.0...(no
debugging symbols found)...done.
Loaded symbols for
/home/kyle/buildroot/buildroot/output/target/lib/libcrypt.so.0
Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/lib/libc.so.0...(no
debugging symbols found)...done.
Loaded symbols for /home/kyle/buildroot/buildroot/output/target/lib/libc.so.0
Reading symbols from
/home/kyle/buildroot/buildroot/output/target/lib/ld-uClibc.so.0...(no
debugging symbols found)...done.
Loaded symbols for
/home/kyle/buildroot/buildroot/output/target/lib/ld-uClibc.so.0
Core was generated by `ssh-keygen -t rsa'.
Program terminated with signal 11, Segmentation fault.
#0  0x0804da1a in main ()
(gdb) backtrace
#0  0x0804da1a in main ()
(gdb) up
Initial frame selected; you cannot go up.

Uh, so somewhere I managed to build everything without any debugging
symbols.  I'll try again.  Sigh.  The compile/edit/retry cycle on this
is quite long.  How "smart" is Builtroot when I change configuration?
Will it just rebuild the things I need to rebuild?  I've been doing a
"make clean" before every attempt.

I'm trying!

Best,
Kyle