From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ssh-keygen seg fault
Date: Wed, 19 Jan 2011 11:29:54 +0100 [thread overview]
Message-ID: <87sjwpfaot.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTik4ZfnUpWeg91eWqMXGSxEX-H3c5L6+LDM_BqdU@mail.gmail.com> (Kyle Hayes's message of "Mon, 17 Jan 2011 14:23:21 -0800")
>>>>> "Kyle" == Kyle Hayes <kyle@greenmonitor.com> writes:
Hi,
Kyle> I got a core file. I have a target GDB for use with host programs. I
Kyle> turned off stripping. But...
Kyle> sudo /home/kyle/buildroot/buildroot/output/toolchain/gdbhost-7.1/gdb/gdb
Kyle> /home/kyle/buildroot/buildroot/output/target/usr/bin/ssh-keygen
Kyle> /media/HC/core
You don't need sudo.
You can do this even with stripping, if you point gdb at the unstripped
version in output/build/...
To get gdb to find the correct shared libs, you'll need to do
set solib-absolute-prefix path/to/output/staging
Kyle> Uh, so somewhere I managed to build everything without any debugging
Kyle> symbols. I'll try again. Sigh. The compile/edit/retry cycle on this
Kyle> is quite long. How "smart" is Builtroot when I change configuration?
Kyle> Will it just rebuild the things I need to rebuild? I've been doing a
Kyle> "make clean" before every attempt.
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
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-19 10:29 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 [this message]
2011-01-19 17:50 ` Kyle Hayes
2011-01-19 19:14 ` Peter Korsgaard
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=87sjwpfaot.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