From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 13 release -- 2022-11-19 update
Date: Wed, 23 Nov 2022 16:54:50 +0100 [thread overview]
Message-ID: <baa3c6bd2e750ae2acc552996193becd10a56749.camel@skynet.be> (raw)
In-Reply-To: <Y3jPUKR1obaGkpo6@adacore.com>
On Sat, 2022-11-19 at 16:42 +0400, Joel Brobecker via Gdb-patches wrote:
>
> * [PhilippeW]
> Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno
>
> v4 (2022-11-12) below, approved Nov 18th:
> https://sourceware.org/pipermail/gdb-patches/2022-November/193758.html
This has been pushed now.
Thanks for Tom for the review and for Simon for reporting regressions
and reviewing the fixes.
As part of the testing of these fixes, valgrind detected a "use of unitialized bit value".
I have sent an RFA with a fix (was sent twice by mistake, the second one is at:
https://sourceware.org/pipermail/gdb-patches/2022-November/194088.html
This fix is likely good to put in 13.0
Thanks
Philippe
>
> * [TomT] PR symtab/29105
> new DWARF reader still slow
> https://sourceware.org/bugzilla/show_bug.cgi?id=29105
>
> The subject of this PR and the initial message mention that
> the index cache is still faster than the new DWARF reader.
> But reading following discussions, it's not clear to me
> anymore what this ticket is about, or what's left to do.
> I will follow up on the PR itself.
>
prev parent reply other threads:[~2022-11-23 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 12:42 Joel Brobecker
2022-11-19 14:55 ` Philippe Waroquiers
2022-11-20 14:55 ` Rainer Orth
2022-11-22 15:10 ` Simon Marchi
2022-11-22 15:31 ` Joel Brobecker
2022-11-22 15:34 ` Simon Marchi
2022-11-23 15:54 ` Philippe Waroquiers [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=baa3c6bd2e750ae2acc552996193becd10a56749.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).