From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: GDB 8.3 release -- 2019-01-11 update
Date: Fri, 11 Jan 2019 21:31:00 -0000 [thread overview]
Message-ID: <1547242289.5979.3.camel@skynet.be> (raw)
In-Reply-To: <20190111095332.GB22922@adacore.com>
On Fri, 2019-01-11 at 13:53 +0400, Joel Brobecker wrote:
> Hello again,
>
> New update for the GDB-8.3 release. Reminder: The target date
> for creating the branch is:
>
> Tue Jan 15th
>
> The wiki page for tracking known issues is at:
>
> https://sourceware.org/gdb/wiki/GDB_8.3_Release
>
> Fixed since the last update:
>
> * [JoelB] <NO PR>
> GDB crash re-running program on Windows
>
> Fix in review:
> https://www.sourceware.org/ml/gdb-patches/2018-12/msg00443.html
>
> * [KeithS] gdb/23712 (**inherited from 8.2.1**)
> dw2_add_symbol_to_list language assertion
>
> https://www.sourceware.org/ml/gdb-patches/2019-01/msg00231.html
> Well done, Keith, and thanks to everyone who participated in
> all the discussions!
>
> * [SimonM] gdb/23893
> Search paths for debug files for remote debuggee checks are broken
> https://sourceware.org/bugzilla/show_bug.cgi?id=23893
>
> Known blocking issues:
>
> * [TomT/Joel] <NO PR>
> GDB UI word wrapping broken/interferes with 'set style'
> https://www.sourceware.org/ml/gdb-patches/2018-12/msg00435.html
> https://www.sourceware.org/ml/gdb-patches/2019-01/msg00098.html
>
> From what I can tell, "set style enabled off" doesn't prevent
> the problem from happening either. Tom indicated in his last
> message he has a fix, and just needs a testcase.
I did some manual test in a corner with the patch. The patch
improves significantly, but there are still one or two things
not ok (see msg00098.html thread).
Regarding the style, it would be really nice to have:
https://sourceware.org/ml/gdb-patches/2018-12/msg00449.html
as otherwise, set|show style online help/behaviour is
inconsistent with the other set|show.
It would be nice to have
https://sourceware.org/ml/gdb-patches/2019-01/msg00227.html
(as GDB will color more file names, functions
and addresses).
Thanks
Philippe
>
> I will try to run it against AdaCore's testsuite, which hit
> that issue quite a bit, so probably a good testbed too.
>
> Looking at the PRs marked 8.3 as the milestone, I also see...
>
> * [TomT] tui/20819
> Binding Control-j in inputrc breaks "layout asm"
> https://sourceware.org/bugzilla/show_bug.cgi?id=20819
>
> ... but i don't understand why this would be blocking for 8.3.
> It would be nice to have a way to get a more detailed history
> of the changes made to the status of that PR so we can determine
> when it was marked 8.3. My suspicion is that it was marked 8.3
> when fixed by Tom, and then the PR got re-opened (around Jan 2nd)
> due to a regression.
>
> Tom - do you confirm this is not a critical bug, other than
> maybe the regression, in which case it would be sufficient to
> simply revert?
>
> Any other issue, please let us know...
>
> Thank you!
next prev parent reply other threads:[~2019-01-11 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 9:53 Joel Brobecker
2019-01-11 10:36 ` Eli Zaretskii
2019-01-11 13:41 ` Joel Brobecker
2019-01-11 16:10 ` Eli Zaretskii
2019-01-11 21:31 ` Philippe Waroquiers [this message]
2019-01-13 5:25 ` Joel Brobecker
[not found] ` <87sgxyojb3.fsf@tromey.com>
2019-01-13 5:22 ` 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=1547242289.5979.3.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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