Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 8.3 release update (2019-03-25)
Date: Tue, 26 Mar 2019 21:15:00 -0000	[thread overview]
Message-ID: <87ef6t2v8p.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190325204307.GA21459@adacore.com>

Joel Brobecker <brobecker@adacore.com> writes:

> To me, it looks like all issues reported for that version
> have been fixed?

Hello,

There is a regression that affects the release branch and causes some
control characters to be printed infinitely when listing source files
(see <https://sourceware.org/ml/gdb-patches/2019-03/msg00611.html>).
This one isn't fixed.

There is a testsuite issue that was fixed in
<https://sourceware.org/ml/gdb-patches/2019-03/msg00142.html>
(gdb/testsuite: Prepare for DejaGnu 1.6.2), but I haven't seen the
corresponding commit in gdb-8.3-branch.  The commit that causes the
issue is in the branch.  I posted a message in that thread asking if it
makes sense to include it in the release branch.

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>.


Thanks!
--
Pedro Franco de Carvalho


  parent reply	other threads:[~2019-03-26 21:15 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 [this message]
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

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=87ef6t2v8p.fsf@linux.vnet.ibm.com \
    --to=pedromfc@linux.ibm.com \
    --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