From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Prevent pagination in GDB_INTERNALFLAGS
Date: Mon, 26 Oct 2020 10:54:02 -0400 [thread overview]
Message-ID: <81c4eda5-471c-8c6c-d995-590354de87b9@polymtl.ca> (raw)
In-Reply-To: <20201026090134.GA27913@delia>
On 2020-10-26 5:01 a.m., Tom de Vries wrote:
> Hi,
>
> When running test-case gdb.base/corefile.exp with target board readnow, we run
> into:
> ...
> Reading symbols from outputs/gdb.base/corefile/corefile...^M
> Expanding full symbols from outputs/gdb.base/corefile/corefile...^M
> [New LWP 2293]^M
> Core was generated by `outputs/gdb.base/corefile/co'.^M
> Program terminated with signal SIGABRT, Aborted.^M
> --Type <RET> for more, q to quit, c to continue without paging--\
> FAIL: gdb.base/corefile.exp: (timeout) starting with -core
> ...
>
> In commit bd447abb24 "Make gdb.base/corefile.exp work on terminals with few
> rows", pagination (in the same test-case) is prevented using:
> ...
> set stty_init "rows 25 cols 80"
> ...
> but this doesn't work in our case because using -readnow adds an extra line
> "Expanding full symbols".
>
> The test passes when increasing rows to 26. However, increasing the rows by
> some n only fixes the problem for n lines, and things will break again if
> somehow we end up with n + 1 lines.
>
> Instead, fix this by setting heigth and width in INTERNAL_GDBFLAGS. This
> solution was not chosen in commit bd447abb24 because it doesn't handle
> pagination due to the introduction text. But it does handle the pagination
> due to the extra "Expanding full symbols", and any other line printed during
> and after file loading.
>
> Tested on x86_64-linux, with and without readnow.
>
> With -readnow, fixes these FAILs:
> ...
> FAIL: gdb.base/corefile.exp: (timeout) starting with -core
> FAIL: gdb.base/reread-readsym.exp: source reread-readsym.gdb 1 (timeout)
> ...
>
> Any comments?
>
> Thanks,
> - Tom
I don't see the failures on Ubuntu 20.04. The set of lines printed when
loading the core are probably a bit different depending on the distro,
which libraries are loaded, etc. But I think I can reproduce it if I
reduce the rows to 20 in stty_init.
The patch LGTM.
Simon
prev parent reply other threads:[~2020-10-26 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 9:01 Tom de Vries
2020-10-26 14:54 ` Simon Marchi via Gdb-patches [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=81c4eda5-471c-8c6c-d995-590354de87b9@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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