From: Simon Marchi <simon.marchi@polymtl.ca>
To: Phillip Raffeck <phillip.raffeck@fau.de>, gdb@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 10.1 breaks Linux lx-symbols
Date: Wed, 27 Jan 2021 10:44:12 -0500 [thread overview]
Message-ID: <767c0e82-6a84-c429-5a45-60708df69a29@polymtl.ca> (raw)
In-Reply-To: <20210127122059.4qtoiuzbexyxrmgz@fillepad.localdomain>
On 2021-01-27 7:20 a.m., Phillip Raffeck wrote:
> Hi,
>
> the value subscript bug present in 10.1 and fixed in commit
> 5b56203a7cadd545b33713e98e274e582242e090 breaks, among others, the
> lx-symbols command from the Linux kernels gdb scripts, as these rely on
> iterating the sections of the loaded modules, which in turn uses array
> subscripting.
>
> As the bug fix has already made it into branch gdb-10-branch, are there
> any plans to release a version 10.2 with bug fixes any time soon?
>
> Note: I know, you're not responsible for the gdb scripts of the Linux
> kernel, I just wanted give a real-world example of consequences stemming
> from that bug.
>
> Best regards
> Phillip Raffeck
>
Hi!
It all depends on our release manager, Joel, but yes in theory GDB 10.2 is
coming eventually, I just can't tell when.
I have some more series I would like to propose for GDB 10, but they are
pending review.
[PATCH 00/13] DWARF 5 rnglists & loclists fixes (PR 26813)
https://sourceware.org/pipermail/gdb-patches/2021-January/175221.html
[PATCH 0/4] Fix CU expansion queue-related problems
https://sourceware.org/pipermail/gdb-patches/2020-November/173372.html
Simon
next prev parent reply other threads:[~2021-01-27 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 12:20 Phillip Raffeck
2021-01-27 15:44 ` Simon Marchi [this message]
2021-01-28 3:14 ` Joel Brobecker
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=767c0e82-6a84-c429-5a45-60708df69a29@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=phillip.raffeck@fau.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).