From: adrian.freihofer@gmail.com
To: Christopher Larson <kergoth@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v8 3/8] image-combined-dbg: make this the default
Date: Wed, 15 Nov 2023 23:32:55 +0100 [thread overview]
Message-ID: <b38107c74191ff9a5fa6fb0a9cf8a42cfed32225.camel@gmail.com> (raw)
In-Reply-To: <b98adc29-7e18-4c68-b94c-4b9b5b2a38db@Spark>
On Wed, 2023-11-15 at 09:26 -0700, Christopher Larson wrote:
>
> Can you explain your issues with gdb with using a rootfs-dbg, because
> I don’t see any problem with a filesystem that only contains debug
> symbols, given how easily gdb can be configured to look into
> alternate paths. I’ll admit I also don’t know the difference between
> these modes, and also wonder how IMAGE_GEN_DEBUGFS relates.
>
>
It simply does not find the symbols if only the rootfs-dbg is
available. If this class
https://git.yoctoproject.org/poky/tree/meta/classes-recipe/image-combined-dbg.bbclass
is added to the build it just works.
Since this is not too obvious, I wondered if it wouldn't be better if
the combined debugfs were the default behavior. Then Ross asked the
same question and I developed a patch to simplify this.
But either way, there are too many unanswered questions to change a
well-established default behavior. And there are other ways to deal
with it.
Thank you for pointing this out.
next prev parent reply other threads:[~2023-11-15 22:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 11:01 [PATCH v8 0/8] devtool ide plugin Adrian Freihofer
2023-11-01 11:01 ` [PATCH v8 1/8] vscode: add minimal configuration Adrian Freihofer
2023-11-01 11:01 ` [PATCH v8 2/8] cmake.bbclass: support qemu Adrian Freihofer
2023-11-06 13:39 ` [OE-core] " Richard Purdie
2023-11-01 11:01 ` [PATCH v8 3/8] image-combined-dbg: make this the default Adrian Freihofer
2023-11-06 13:50 ` [OE-core] " Richard Purdie
2023-11-15 14:21 ` adrian.freihofer
2023-11-15 16:26 ` Christopher Larson
2023-11-15 22:32 ` adrian.freihofer [this message]
2023-11-20 22:53 ` Peter Kjellerstedt
2023-11-21 8:58 ` Enguerrand de Ribaucourt
2023-11-22 12:23 ` [OE-core] " adrian.freihofer
2023-11-22 12:25 ` Alexander Kanavin
2023-11-22 12:35 ` adrian.freihofer
2023-11-01 11:01 ` [PATCH v8 4/8] tests: add a C++ example recipe Adrian Freihofer
2023-11-01 11:01 ` [PATCH v8 5/8] devtool: refactor deploy-target Adrian Freihofer
2023-11-06 14:05 ` [OE-core] " Richard Purdie
2023-11-01 11:01 ` [PATCH v8 6/8] devtool: new ide plugin Adrian Freihofer
2023-11-06 14:24 ` [OE-core] " Richard Purdie
2023-11-15 14:01 ` adrian.freihofer
2023-11-15 14:54 ` Richard Purdie
2023-11-15 15:33 ` adrian.freihofer
2023-11-01 11:01 ` [PATCH v8 7/8] oe-selftest devtool: ide tests Adrian Freihofer
2023-11-01 11:01 ` [PATCH v8 8/8] docs: cover devtool ide Adrian Freihofer
2023-11-02 10:11 ` [OE-core] " Quentin Schulz
2023-11-02 22:36 ` adrian.freihofer
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=b38107c74191ff9a5fa6fb0a9cf8a42cfed32225.camel@gmail.com \
--to=adrian.freihofer@gmail.com \
--cc=kergoth@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.