From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Victor Kamensky <kamensky@cisco.com>,
openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alexander.kanavin@intel.com>
Subject: Re: [PATCH v2 1/5] image: add image-combined-dbg helper class
Date: Tue, 03 Apr 2018 18:43:52 +0100 [thread overview]
Message-ID: <1522777432.11431.248.camel@linuxfoundation.org> (raw)
In-Reply-To: <1522776217-23250-2-git-send-email-kamensky@cisco.com>
On Tue, 2018-04-03 at 10:23 -0700, Victor Kamensky wrote:
> There is IMAGE_GEN_DEBUGFS="1" variable that enables build of
> additional rootfs-dbg and additional archive that contains
> complimentary symbols files for a given image. But the issue
> with this resulting directory and tarball that before use it
> has to be combined with original image content. It is required
> since all cross debugging tools like gdb, perf, and systemtap
> need file system that contains both target executables/libraries
> and their symbols. Those tools need to find executable/library
> first and through it debuglink note find corresponding symbols
> file.
>
> image-combined-dbg when added to USER_CLASSES just copies
> final resulting rootfs back into rootfs-dbg creating combined
> target and debug symbols rootfs that can be used for debugging
> directly.
>
> Signed-off-by: Victor Kamensky <kamensky@cisco.com>
> ---
> meta/classes/image-combined-dbg.bbclass | 9 +++++++++
> meta/classes/image.bbclass | 1 +
> 2 files changed, 10 insertions(+)
> create mode 100644 meta/classes/image-combined-dbg.bbclass
>
> diff --git a/meta/classes/image-combined-dbg.bbclass
> b/meta/classes/image-combined-dbg.bbclass
> new file mode 100644
> index 0000000..a709adf
> --- /dev/null
> +++ b/meta/classes/image-combined-dbg.bbclass
> @@ -0,0 +1,9 @@
> +IMAGE_PREPROCESS_COMMAND_append = " combine_dbg_image; "
> +
> +combine_dbg_image () {
> + if [ "$IMAGE_GEN_DEBUGFS" = "1" -a -e ${IMAGE_ROOTFS}-dbg ];
Can you not just use ${IMAGE_GEN_DEBUGFS} and drop the export?
Cheers,
Richard
next prev parent reply other threads:[~2018-04-03 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 17:23 [PATCH v2 0/5] systemtap adding sysroot, cross compiling of user land related scripts Victor Kamensky
2018-04-03 17:23 ` [PATCH v2 1/5] image: add image-combined-dbg helper class Victor Kamensky
2018-04-03 17:43 ` Richard Purdie [this message]
2018-04-03 17:23 ` [PATCH v2 2/5] Revert "systemtap: Cross compilation fix" Victor Kamensky
2018-04-03 17:23 ` [PATCH v2 3/5] systemtap: support --sysroot option in variety of situations in cross build Victor Kamensky
2018-04-03 17:23 ` [PATCH v2 4/5] systemtap: create translator packageconfig Victor Kamensky
2018-04-03 17:23 ` [PATCH v2 5/5] crosstap: replace script with new python based implementation Victor Kamensky
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=1522777432.11431.248.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@intel.com \
--cc=kamensky@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox