Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Mathieu Othacehe" <othacehe@gnu.org>, <docs@lists.yoctoproject.org>
Subject: Re: [PATCH v3 0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable
Date: Mon, 17 Feb 2025 10:00:26 +0100	[thread overview]
Message-ID: <D7ULJGLDCLNM.2F5SN59SUVGYR@bootlin.com> (raw)
In-Reply-To: <20250211161239.5396-1-othacehe@gnu.org>

Hi Mathieu,

On Tue Feb 11, 2025 at 5:12 PM CET, Mathieu Othacehe wrote:
> Hello,
>
> That series is introducing a PACKAGE_KEEP_DEBUG_FRAME variable that can be
> used to keep the .debug_frame ELF section when stripping packages.
>
> It is then building upon that to present how to get human-readable backtraces
> on target, possibly also relying on the minidebuginfo mechanism.
>
> Thanks,
>
> Mathieu
>
> v2: https://lists.yoctoproject.org/g/docs/message/6252
> poky: https://git.yoctoproject.org/poky/commit/?h=master-next&id=10448200b63bdc45b39504ebcddd85b5f274f0c4

This link does not work for me. Could you give me a new link with your
commits, on master? I couldn't find them.

Thank you,
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2025-02-17  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 16:12 [PATCH v3 0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable Mathieu Othacehe
2025-02-11 16:12 ` [PATCH v3 1/2] profile-manual: " Mathieu Othacehe
2025-02-11 16:12 ` [PATCH v3 2/2] dev-manual/debugging: Add a "Backtraces or target" section Mathieu Othacehe
2025-02-17  9:00 ` Antonin Godard [this message]
2025-02-17 10:12   ` [PATCH v3 0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable Mathieu Othacehe
2025-02-17 14:47     ` [docs] " Richard Purdie

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=D7ULJGLDCLNM.2F5SN59SUVGYR@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=othacehe@gnu.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