From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: ptxdist <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Should GDB select XZ?
Date: Thu, 9 May 2024 12:15:08 +0200 [thread overview]
Message-ID: <ZjyiLCAeQVIHeOOV@pengutronix.de> (raw)
In-Reply-To: <3ec54e2f-eb27-4b3d-a73f-4bb3d937a136@mev.co.uk>
On Tue, May 07, 2024 at 02:39:01PM +0100, Ian Abbott wrote:
> The configure script of GDB (version 7.6 or later) has a --with-lzma option
That's definitely old enough, so we can rely on the option to be available.
gdb is always a bit tricky because we need to support multiple versions.
> that controls whether GDB will use liblzma or not. (It is needed to for
> reading .gnu_debuginfo sections from ELF files, if they are present.) By
> default (if not explicitly enabled or disabled), it will use liblzma if it
> is detected at build time.
>
> Currently, PTXdist does not configure GDB with any --with-lzma value, so
> whether or not it is configured to use liblzma depends on whether some
> version of XZ has previously been built or not.
>
> If GDB gets automatically configured to use liblzma, but the XZ package is
> not to be installed (perhaps there is a previous build of XZ in the
> platform's sysroot-target), then there will be a run-time error when running
> GDB due to the missing library. It also means that the build of GDB may not
> be reproducible.
>
> It seems to me that PTXdist should have a configuration option to choose
> whether GDB should be built with liblzma support or not (and possibly a
> configuration option to select whether the GDB version is 7.6 or later,
> defaulting to true). The default could depend on
> PTXCONF_TARGET_MINI_DEBUGINFO. If binaries have a .gnu_debuginfo section
> then we probably want GDB to be able to use it!
Right, gdb should definitely be able to read .gnu_debuginfo sections. I
just never noticed this because I always use gdbserver.
As you probably noticed by now, depending on PTXCONF_TARGET_MINI_DEBUGINFO
does not work because it is defined in the platformconfig and gdb is not.
> I'll attempt to knock up a patch for it.
I appreciate it. The gdb package has seen little updated in the past
because I don't actually use it myself. So fixes from someone who actually
uses it are welcome.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-05-09 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 13:39 Ian Abbott
2024-05-09 10:15 ` Michael Olbrich [this message]
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=ZjyiLCAeQVIHeOOV@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=abbotti@mev.co.uk \
--cc=ptxdist@pengutronix.de \
/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