From: Jan Kratochvil <jkratoch@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed] Fix PR tui/21216: TUI line breaks regression
Date: Fri, 10 Mar 2017 14:04:00 -0000 [thread overview]
Message-ID: <20170310140450.GA5206@host1.jankratochvil.net> (raw)
In-Reply-To: <f263c39c-813f-35bb-824f-69a9de62068b@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Fri, 10 Mar 2017 14:33:39 +0100, Pedro Alves wrote:
> See test patch below, and attached resulting gdb.log. Note that viewing
> the log with "less" on the terminal directly "hides" some of the escape
> sequences (they get interpreted directly).
Running gdb/testsuite/gdb.tui/tui-nl-filtered-output.exp ...
+PASS: gdb.tui/tui-nl-filtered-output.exp: show environment
PASS: gdb.tui/tui-nl-filtered-output.exp: tui enable
+PASS: gdb.tui/tui-nl-filtered-output.exp: show height
PASS: gdb.tui/tui-nl-filtered-output.exp: set pagination on
PASS: gdb.tui/tui-nl-filtered-output.exp: set height 2000
+PASS: gdb.tui/tui-nl-filtered-output.exp: set height 2000
+PASS: gdb.tui/tui-nl-filtered-output.exp: set height 2000
+PASS: gdb.tui/tui-nl-filtered-output.exp: set height 2000
+FAIL: gdb.tui/tui-nl-filtered-output.exp: set height 2000 (timeout)
PASS: gdb.tui/tui-nl-filtered-output.exp: correct line breaks
Thanks,
Jan
[-- Attachment #2: tui-nl-filtered-output2.out.xz --]
[-- Type: application/x-xz, Size: 2940 bytes --]
next prev parent reply other threads:[~2017-03-10 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 0:19 Pedro Alves
2017-03-09 23:04 ` Jan Kratochvil
2017-03-10 12:59 ` Jan Kratochvil
2017-03-10 13:33 ` Pedro Alves
2017-03-10 14:04 ` Jan Kratochvil [this message]
2017-03-10 17:20 ` Pedro Alves
2017-03-10 17:27 ` Jan Kratochvil
2017-03-10 18:17 ` Pedro Alves
2017-03-10 18:46 ` Jan Kratochvil
2017-03-10 18:55 ` Pedro Alves
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=20170310140450.GA5206@host1.jankratochvil.net \
--to=jkratoch@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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