All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Enguerrand de Ribaucourt" <enguerrand.de-ribaucourt@savoirfairelinux.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v6 03/12] devtool: new ide plugin
Date: Tue, 14 Nov 2023 00:47:28 -0800	[thread overview]
Message-ID: <3856.1699951648610019974@lists.openembedded.org> (raw)
In-Reply-To: <186EDB03-6E99-4675-BDAA-A19FD95EC95F@arm.com>

On Thu, Oct 12, 2023 at 02:53 PM, Ross Burton wrote:

>
> I’d not noticed image-combined-dbg existed and do wonder if that shoud be
> the behaviour of the debug rootfs. Is there actually a use-case for a tarball
> which is _just_ the symbols?
>

The use for a rootfs containing just the debug tarballs is explicited in the documentation here: https://docs.yoctoproject.org/4.0.4/singleindex.html#using-the-gdbserver-method

$ tar xvfj build-dir/tmp-glibc/deploy/images/machine/image.rootfs.tar.bz2
$ tar xvfj build-dir/tmp-glibc/deploy/images/machine/image-dbg.rootfs.tar.bz2

This debug-rootfs is "combined" with the rootfs image which already contains the binaries. It could also be done at runtime on a live target (through tar, overlayfs, ...).

The later patch-set makes image-combined-dbg the default which makes the debug-rootfs already containing the image rootfs. This would not produce an error with those tar commands because they silently overwrite existing files. However, it would break some users setups with these conditions:
 a. The user has another way for combining the rootfs and dbg rootfs which produces an error if files exist in both archives
 b. The user has storage limitations for the dbg rootfs which would be exceeded when adding the binaries to it
 c. The user customizes the original rootfs output. These customizations would be lost when combining.
 d. The user is extracting the debug rootfs on a runtime rootfs with runtime modifications

An example for C is wic fstab customization, or any modifications which happen at the do_rootfs step:

     do_rootfs_postprocess() {
         echo "Customized issue" >> ${IMAGE_ROOTFS}/etc/issue
     }

     addtask do_rootfs_postprocess after do_rootfs before do_image

When extracting the debug-rootfs with image-combined-dbg, this customization gets lost because the debug-rootfs contains the original files from the package.

That's why I suggest keeping the debug-rootfs as it is and keep image-combined-debug as a separate option.


  parent reply	other threads:[~2023-11-14  8:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 15:52 [OE-core][PATCH v6 00/12] devtool ide plugin Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 01/12] vscode: add minimal configuration Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 02/12] cmake.bbclass: support qemu Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 03/12] devtool: new ide plugin Adrian Freihofer
2023-10-12 12:53   ` Ross Burton
2023-10-30 21:33     ` adrian.freihofer
2023-11-14  8:47     ` Enguerrand de Ribaucourt [this message]
2023-09-10 15:52 ` [OE-core][PATCH v6 04/12] tests: add a C++ example recipe Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 05/12] cpp-example: workaround for pseudo breakeage Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 06/12] refactor: make multiprocess_launch callable without d Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 07/12] refactor: make strip_execs " Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 08/12] devtool: refactor deploy-target Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 09/12] devtool: ide make deploy-target quicker Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 10/12] oe-selftest devtool: refactor runqemu pre-requisites Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 11/12] oe-selftest devtool: ide tests Adrian Freihofer
2023-09-10 15:52 ` [OE-core][PATCH v6 12/12] docs: cover devtool ide Adrian Freihofer
2023-09-11 11:54   ` Michael Opdenacker

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=3856.1699951648610019974@lists.openembedded.org \
    --to=enguerrand.de-ribaucourt@savoirfairelinux.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.