Thanks folks, IMAGE_GEN_DEBUGFS was exactly what I was looking for.
--wpd
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49430): https://lists.yoctoproject.org/g/yocto/message/49430
Mute This Topic: https://lists.yoctoproject.org/mt/74229522/21656
I know I can do
$ bitbake base-image -cpopulate_sdk
and distribute the resulting SDK to developers (myself included).
But suppose I've just built and deployed an image and want to debug a
core file generated by one of the applications.
I don't see .debug directories anywhere in $TMP, so when I
On Mon, Apr 6, 2020 at 3:34 PM Patrick Doyle wrote:
>
> I have a recipe that looks something like this (I'm simplifying a bit here):
>
> SRC_URI += "${EXTERNAL_URL}"
>
> do_compile() {
> do -something -with $(basename ${EXTERNAL_URL} .ext)
> }
I have a recipe that looks something like this (I'm simplifying a bit here):
SRC_URI += "${EXTERNAL_URL}"
do_compile() {
do -something -with $(basename ${EXTERNAL_URL} .ext)
}
where EXTERNAL_URL is supplied in the environment when invoking
Bitbake (and is whitelisted in the environment).
The
On Wed, Mar 11, 2020 at 1:26 PM Patrick Doyle via
Lists.Yoctoproject.Org
wrote:
> I want the daemon to run as a non-root user, so I have "inherit
> extrausers" in my recipe.
>
> Suppose I only wanted to create that extra user iff the package
> containing the daemon
I may be overthinking/overtweaking this but...
I have a recipe with that creates a number of executables, one of
which is a daemon.
I have split that daemon off into its own separate package using the
PACKAGES =+ "${PN]-blah-blah-blah" construct.
I want the daemon to run as a non-root user, so
On Thu, Feb 20, 2020 at 4:18 PM Khem Raj wrote:
> On Thu, 2020-02-20 at 08:52 -0500, Patrick Doyle wrote:
> > I am trying to understand why I can't get stack traces from cores
> > file
> > on a mipsel system. At the moment (after strategic additions of
> > bre
On Wed, Feb 19, 2020 at 5:19 PM Richard Purdie
wrote:
> On Tue, 2020-02-18 at 11:26 -0500, Patrick Doyle wrote:
> > Does anybody have any tips or tricks for how I might debug the
> > (cross-canadian) gdb built by Yocto's SDK?
> Do you perhaps want gdb-cross-mipsel ?
>
> cr
Does anybody have any tips or tricks for how I might debug the
(cross-canadian) gdb built by Yocto's SDK?
I need to add some printf's to the gdb code to help track down why
something isn't working, but none of my traditional
get-ready-to-debug-this-code techniques are working.
How can I run the
i was just reviewing a recipe I wrote a month or two ago and saw that I wrote:
do_compile() {
python3 ${WORKDIR}/assemble-tsk-blob.py -o tsk-blob -d
${DEPLOY_DIR_IMAGE}/foo -t ${DEPLOY_DIR_IMAGE}/bar
}
and I thought to myself, why did I write assemble-tsk-blob.py (which
is a fairly trivial
10 matches
Mail list logo
