From: Tom Tromey <tromey@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>,
gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
Tom Tromey <tromey@adacore.com>
Subject: Re: GDB 8.3 release update (2019-03-25)
Date: Wed, 27 Mar 2019 13:30:00 -0000 [thread overview]
Message-ID: <87imw4zbpl.fsf@tromey.com> (raw)
In-Reply-To: <20190326222103.GD6837@adacore.com> (Joel Brobecker's message of "Tue, 26 Mar 2019 15:21:03 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> 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.
Joel> Thanks for bringing it to our attention. This is very annoying.
Joel> Does it happen all the time, or only under specific circumstances?
Joel> In other words, I'm wondering if we have some kind of workaround.
Joel> Tom - would you be OK to put this on your list to look at, sometime?
Sure thing. I think there's already a patch.
Tom
next prev parent reply other threads:[~2019-03-27 13:30 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 [this message]
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=87imw4zbpl.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=pedromfc@linux.ibm.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