From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 10.1 release -- 2020-09-18 Update
Date: Fri, 18 Sep 2020 21:37:21 -0400 [thread overview]
Message-ID: <e5f497c1-5d57-c249-dcd2-59f15e33ee61@simark.ca> (raw)
In-Reply-To: <20200918234602.GA4674@adacore.com>
On 2020-09-18 7:46 p.m., Joel Brobecker wrote:
> Hello,
>
> A quick update on the release status since the 10.0.90 pre-release
> was published last Saturday...
>
> So far, we don't have anything really worrisome that could significantly
> delay the release. I'll try to find some time to test the gnulib patches
> that Eli pointed out next week.
Huh, the patch to skip the endbr32 instruction in prologues kind of fell
through the cracks until today. It was just merged to master. Should
we consider it for the release branch? If you don't have it and your
compiler inserts these instructions, it kind of screws up the debugging
experience, since the function prologues are never properly skipped. In
my experience, this results in GDB showing wrong argument values when
reaching a function breakpoint, for example.
The patch in question is:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=14f9473ca225290680c8b21240cdca49f8d3b332
Simon
next prev parent reply other threads:[~2020-09-19 1:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 23:46 Joel Brobecker
2020-09-19 1:37 ` Simon Marchi [this message]
2020-09-19 19:42 ` Joel Brobecker
2020-09-19 23:58 ` Simon Marchi
2020-09-19 7:41 ` Eli Zaretskii
2020-09-19 19:48 ` Joel Brobecker
2020-09-21 16:26 ` Eli Zaretskii
2020-09-26 17:39 ` Joel Brobecker
2020-09-28 9:30 ` Eli Zaretskii via Gdb-patches
2020-09-28 20:11 ` Joel Brobecker
2020-10-09 19:53 ` [pushed/gdb-10-branch] gnulib: fix stat/fstat build errors on old Windows version or using old MinGW Joel Brobecker
2020-09-20 1:03 ` GDB 10.1 release -- 2020-09-18 Update Simon Marchi
2020-09-20 6:09 ` Eli Zaretskii
2020-09-21 19:54 ` Simon Marchi
2020-09-23 13:39 ` Tom Tromey
2020-09-23 14:00 ` Simon Marchi
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=e5f497c1-5d57-c249-dcd2-59f15e33ee61@simark.ca \
--to=simark@simark.ca \
--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