From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ssh-keygen seg fault
Date: Wed, 19 Jan 2011 20:14:36 +0100 [thread overview]
Message-ID: <87d3nsg0yr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTinJ1e9Q9V0YscnQ=s9ALVyvbJn_bZYPLeLeee+A@mail.gmail.com> (Kyle Hayes's message of "Wed, 19 Jan 2011 09:50:11 -0800")
>>>>> "Kyle" == Kyle Hayes <kyle@greenmonitor.com> writes:
Hi,
>> Buildroot handles small changes like adding a package quite well, but
>> for global changes like toolchain options or strip/no-strip you'll need
>> to make clean; make
Kyle> I think something I'm doing is still incorrect:
Kyle> kyle at hp-workstation:~/buildroot/buildroot$
Kyle> ./output/toolchain/gdbhost-7.1/gdb/gdb
Normally you would use output/staging/usr/bin/$PREFIX-gdb, but OK.
Kyle> GNU gdb (GDB) 7.1
Kyle> Copyright (C) 2010 Free Software Foundation, Inc.
Kyle> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
Kyle> This is free software: you are free to change and redistribute it.
Kyle> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
Kyle> and "show warranty" for details.
Kyle> This GDB was configured as "--host=i686-pc-linux-gnu
Kyle> --target=i486-unknown-linux-uclibc".
Kyle> For bug reporting instructions, please see:
Kyle> <http://www.gnu.org/software/gdb/bugs/>.
Kyle> (gdb) set solib-absolute-prefix
Kyle> /home/kyle/buildroot/buildroot/output/staging/lib/
Don't add lib at the end. solib-absolute-prefix is a PREFIX, not the
location of the library files.
Kyle> (gdb) file output/target/usr/bin/ssh-keygen
Kyle> Reading symbols from
Kyle> /home/kyle/buildroot/buildroot/output/target/usr/bin/ssh-keygen...done.
Again, please point gdb at the unstripped version in
output/build/openssh*/ssh-keygen instead of the (potentially) stripped
version in target.
Kyle> If I run ssh-keygen on the command line on the target machine, I get a
Kyle> seg fault and I get "ssh-keygen used greatest stack depth: 6460 bytes
Kyle> left" I have stack smashing protection turned on. Is this an
Kyle> infinite recursion problem or just a normal output from the system
Kyle> about this? Other commands from busybox do not print out this error
Kyle> about the stack.
Sorry. don't know. I've never uses the SSP stuff.
Kyle> I tried adding 'no-asm' to the list of options for openssl and
Kyle> rebuilding that (just a make at the top level does not rebuild
Kyle> openssl, is that correct behavior?). I get the same behavior.
Rebuild is controlled by the .stamp_* files inside build/openssl*/, so
it only gets rebuilt if you remove those (or remove the entire openssl
dir). Notice that dependent packages don't get rebuilt automatically.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-19 19:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:29 [Buildroot] ssh-keygen seg fault Kyle Hayes
2011-01-14 8:07 ` Thomas Petazzoni
2011-01-14 9:24 ` Will Moore
2011-01-14 9:40 ` Thomas Petazzoni
2011-01-14 17:00 ` Kyle Hayes
2011-01-14 17:19 ` Thomas Petazzoni
2011-01-14 19:29 ` Kyle Hayes
2011-01-14 21:04 ` Michael S. Zick
2011-01-14 22:04 ` Kyle Hayes
2011-01-14 22:07 ` Kyle Hayes
2011-01-17 22:23 ` Kyle Hayes
2011-01-18 0:12 ` Kyle Hayes
2011-01-19 10:29 ` Peter Korsgaard
2011-01-19 17:50 ` Kyle Hayes
2011-01-19 19:14 ` Peter Korsgaard [this message]
2011-01-19 19:21 ` Kyle Hayes
2011-01-20 16:49 ` Kyle Hayes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3nsg0yr.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox