mbox series

[v3,0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable

Message ID 20250211161239.5396-1-othacehe@gnu.org
Headers show
Series Document the PACKAGE_KEEP_DEBUG_FRAME variable | expand

Message

Mathieu Othacehe Feb. 11, 2025, 4:12 p.m. UTC 
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

Changelog:
v2: Fix a build issue
v3: Document the PACKAGE_KEEP_DEBUG_FRAME
variable rather that the PACKAGE_KEEP_SECTIONS variable because the former
approach was preferred and merged into poky.

Mathieu Othacehe (2):
  profile-manual: Document the PACKAGE_KEEP_DEBUG_FRAME variable.
  dev-manual/debugging: Add a "Backtraces or target" section

 documentation/dev-manual/debugging.rst | 55 ++++++++++++++++++++++++++
 documentation/ref-manual/variables.rst |  9 +++++
 2 files changed, 64 insertions(+)

Comments

Antonin Godard Feb. 17, 2025, 9 a.m. UTC | #1 
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
Mathieu Othacehe Feb. 17, 2025, 10:12 a.m. UTC | #2 
Hello Antonin,

>> 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.

Not sure why that one broke, here's a new one:

https://git.yoctoproject.org/poky/commit/?h=master-next&id=df2c9e884066aafb0dfb60521a4809c5ba4cfd5d

Thanks,

Mathieu
Richard Purdie Feb. 17, 2025, 2:47 p.m. UTC | #3 
On Mon, 2025-02-17 at 11:12 +0100, Mathieu Othacehe via
lists.yoctoproject.org wrote:
> 
> Hello Antonin,
> 
> > > 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.
> 
> Not sure why that one broke, here's a new one:
> 
> https://git.yoctoproject.org/poky/commit/?h=master-next&id=df2c9e884066aafb0dfb60521a4809c5ba4cfd5d

The patch hasn't merged yet, it was queued in master-next which
rebases, hence the ID changes. There are some concerns about the patch,
I'm working on trying to get some feedback about it.

Cheers,

Richard