From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <sundeep.kokkonda@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <randy.macleod@windriver.com>, <raj.khem@gmail.com>
Subject: Re: [OE-core] [PATCH V2] gdb: Upgrade 16.3 -> 17.1
Date: Wed, 24 Dec 2025 10:12:04 +0100 [thread overview]
Message-ID: <DF6BX97B9AVC.XYGAZDNN5E39@bootlin.com> (raw)
In-Reply-To: <20251223094411.2919323-1-sundeep.kokkonda@windriver.com>
On Tue Dec 23, 2025 at 10:44 AM CET, Sundeep KOKKONDA via lists.openembedded.org wrote:
> From: Sundeep KOKKONDA <sundeep.kokkonda@windriver.com>
>
> GDB 17.1 includes the following changes and enhancements:
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-17.1-release
>
> * x86-64 CET shadow stack support
> * Debugging Linux programs that use AArch64 Guarded Control Stacks
> * GDB record feature now supports rv64gc architectures
> * 'info threads' command support for two new options '-stopped' and '-running'
> to limit the list of displayed threads.
> * On Linux and FreeBSD, the addresses shown by the 'info sharedlibrary' command
> are now for the full memory range allocated to the shared library.
> * Linux checkpoints now work with multiple inferiors
> * Improved linker namespace support
> * Warnings and error messages now start with an emoji (warning sign,
> or cross mark) if supported by the host charset. Configurable.
> * Built-in support for TLS on Linux as backup when libthread_db is not
> available. Supported on the x86_64, aarch64, ppc64, s390x, and riscv
> architectures, when compiled with GLIBC or MUSL.
> * New command "set riscv numeric-register-names" to display risc-v
> registers using their numeric names instead of their ABI names.
> * The Alpha target now supports target descriptions.
> * Python API enhancements
> * Support for Python versions older than 3.4 has been removed.
>
> Dropped 0009-Readline-8.3-alpha-release.patch
>
> Signed-off-by: Sundeep KOKKONDA <sundeep.kokkonda@windriver.com>
> ---
Hi Sundeep,
Thanks for your patch.
It looks like this is breaking builds with musl:
ERROR: gdb-17.1-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/x86-64-v3-poky-linux-musl/gdb/17.1/temp/run.do_compile.4040458' failed with exit code 1
...
| ../../sources/gdb-17.1/gdb/ser-unix.c: In function 'void set_custom_baudrate_linux(int, int)':
| ../../sources/gdb-17.1/gdb/ser-unix.c:532:7: error: 'struct termios' has no member named 'c_ospeed'; did you mean '__c_ospeed'?
| 532 | tio.c_ospeed = rate;
| | ^~~~~~~~
| | __c_ospeed
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/2974
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/2939
Can you have a look at this?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-12-24 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 9:44 [PATCH V2] gdb: Upgrade 16.3 -> 17.1 sundeep.kokkonda
2025-12-24 9:12 ` Mathieu Dubois-Briand [this message]
2025-12-31 18:50 ` Dora, Sunil Kumar
2026-02-12 16:59 ` Dora, Sunil Kumar
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=DF6BX97B9AVC.XYGAZDNN5E39@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=sundeep.kokkonda@windriver.com \
/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