From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] store debug information in $HOST_DIR/lib/debug
Date: Mon, 4 Feb 2019 19:19:54 +0100 [thread overview]
Message-ID: <20190204191954.533a4216@windsurf> (raw)
In-Reply-To: <CAAXf6LW961NpVPtOUbmoi4oJeqmtqYWPA8V7FwQP6ztAXdJAKg@mail.gmail.com>
On Mon, 4 Feb 2019 19:05:26 +0100
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> wrote:
> The difference that this patch brings is that now also binaries can be
> debugged based from the target directory, i.e. you don't need to find
> the binary in output/build/foo-version/somewhere/.
>
> Today, the staging directory only contains packages that explicitly
> set FOO_INSTALL_STAGING = YES, which is typically only done for
> libraries.
Yes, but:
1) Typically the binary being debugged has to be passed explicitly as
gdb argument, it's not automatically "inferred" by gdb. So having it
in output/build/foo-<version>/somewhere/ or elsewhere doesn't make a
huge difference.
2) If for convenience reasons we want to make all binaries with
debugging symbols easily available, then the long term solution we
have been discussing for a while is to install all packages to
STAGING_DIR. So basically I'm more for extending STAGING_DIR to
contain binaries rather than to create a partial copy of STAGING_DIR
in HOST_DIR/lib/debug.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-04 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:15 [Buildroot] [PATCH] store debug information in $HOST_DIR/lib/debug Gerhard Heift
2019-01-30 20:28 ` Thomas De Schampheleire
2019-01-31 12:59 ` Gerhard Heift
2019-02-04 16:58 ` Thomas Petazzoni
2019-02-04 18:05 ` Thomas De Schampheleire
2019-02-04 18:19 ` Thomas Petazzoni [this message]
2019-02-04 18:27 ` Yann E. MORIN
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=20190204191954.533a4216@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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