From: Carl Love <cel@us.ibm.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
Carl Love via Gdb <gdb@sourceware.org>
Subject: RE: Question: gdb.tui/tui-layout-asm.exp
Date: Tue, 20 Jul 2021 11:06:54 -0700 [thread overview]
Message-ID: <17fe5c160e330a406af6776e307be95e0e6fab3b.camel@us.ibm.com> (raw)
In-Reply-To: <c80e8e91fa14cd31a3687d245fab81f8fb195064.camel@us.ibm.com>
Andreas:
> Carll re_line \|\s+0x100007b0\s+<__gmon_start__@plt>\s+b\s+0x1000077
> 8\s+<__glink_PLTres\|
> Carll line1 | 0x100007b0 <__gmon_start__@plt> b 0x10000778
> <__glink_PLTresolve> | <-- the read after the wait_for
> read more characters
> Carll match
> false
>
> FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll
> failed)
>
>
> The initial read of line 2, which then becomes re_line has fewer
> characters in it than when the same line is read the second
> time. The
> second read occurs following the wait_for statement.
>
Looking at the screen dumps you can see the output formatting changed
based on the length of the fields.
Initially the dump looks like:
Screen Dump (80 x 24):
0 +------------------------------------------------------------------------------+
1 | 0x100007ac <__libc_start_main@plt> b 0x10000778 <__glink_PLTres|
2 | 0x100007b0 <__gmon_start__@plt> b 0x10000778 <__glink_PLTres|
3 | 0x100007b4 <_fini> lis r2,4098 |
4 | 0x100007b8 <_fini+4> addi r2,r2,32512 |
5 | 0x100007bc <_fini+8> mflr r0 |
After the down key is sent to gdb, the screen dump becomes:
FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll failed)
Screen Dump (80 x 24):
0 +------------------------------------------------------------------------------+
1 | 0x100007b0 <__gmon_start__@plt> b 0x10000778 <__glink_PLTresolve> |
2 | 0x100007b4 <_fini> lis r2,4098 |
3 | 0x100007b8 <_fini+4> addi r2,r2,32512 |
4 | 0x100007bc <_fini+8> mflr r0 |
It looks like the width of the second colum changes one the line with <
__libc_start_main@plt> is no longer being displayed.
I will look to see if we can make the screen width a little wider.
Carl
next prev parent reply other threads:[~2021-07-20 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c9c9f9f9af7ae99468baa7fd885538af4a694714.camel@us.ibm.com>
[not found] ` <20210719164804.GC1688065@embecosm.com>
2021-07-19 22:22 ` Carl Love
2021-07-20 8:01 ` Andreas Schwab
2021-07-20 17:41 ` Carl Love
2021-07-20 18:06 ` Carl Love [this message]
2021-07-20 18:16 ` Carl Love
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=17fe5c160e330a406af6776e307be95e0e6fab3b.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=gdb@sourceware.org \
--cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).