From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>,
gdb-patches@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Re: GDB 8.3 release update (2019-03-25)
Date: Thu, 28 Mar 2019 17:36:00 -0000 [thread overview]
Message-ID: <20190328173633.GA30457@adacore.com> (raw)
In-Reply-To: <54749de1-b15e-0c32-3c3a-31838d1feaf9@redhat.com>
> >> There is another testsuite issue that was fixed, but the fix doesn't seem
> >> to be in the release branch yet
> >> <https://sourceware.org/ml/gdb-patches/2019-03/msg00613.html>.
> > This one, I think is OK, but it isn't as clear. It's not clear also
> > how critical it is for gdb-8.3. Pedro?
>
> It's not critical in the sense that it fixes anything regular uses
> might notice. It fixes a testsuite hang when some testcase hits a tcl
> error, IOW, when a testcase has some buglet. Pedro ran into such a hang
> more than once, so it'd likely help testers if the patch was merged.
> I think the patch itself is pretty low risk. I think it'd be OK to put
> it in the branch.
Thanks for confirming, Pedro. This one is now in gdb-8.3-branch as well.
--
Joel
prev parent reply other threads:[~2019-03-28 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 20:43 Joel Brobecker
2019-03-25 20:51 ` Eli Zaretskii
2019-03-26 20:40 ` Joel Brobecker
2019-03-26 20:46 ` Eli Zaretskii
2019-03-25 22:26 ` Sergio Durigan Junior
2019-03-26 20:48 ` Joel Brobecker
2019-03-26 21:31 ` Sergio Durigan Junior
2019-03-26 22:46 ` Joel Brobecker
2019-03-25 22:29 ` Simon Marchi
2019-03-26 21:15 ` Pedro Franco de Carvalho
2019-03-26 22:21 ` Joel Brobecker
2019-03-27 13:30 ` Tom Tromey
2019-03-27 19:47 ` Pedro Franco de Carvalho
2019-03-27 19:51 ` Pedro Alves
2019-03-28 17:36 ` Joel Brobecker [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=20190328173633.GA30457@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=pedromfc@linux.ibm.com \
--cc=tromey@adacore.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