public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug tui/26922] New: FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll failed)
@ 2020-11-19 16:34 vries at gcc dot gnu.org
  2020-11-19 16:39 ` [Bug tui/26922] " vries at gcc dot gnu.org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: vries at gcc dot gnu.org @ 2020-11-19 16:34 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=26922

            Bug ID: 26922
           Summary: FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of
                    assembler (scroll failed)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tui
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

When running test-case gdb.tui/tui-layout-asm.exp with target board
unix/-fPIE/-pie we run into:
...
FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll failed)
...

Using some printf debugging:
...
index 96fb043321f..20863a6a81b 100644
--- a/gdb/testsuite/gdb.tui/tui-layout-asm.exp
+++ b/gdb/testsuite/gdb.tui/tui-layout-asm.exp
@@ -61,7 +61,12 @@ while (1) {
     if {[Term::wait_for [string_to_regexp $line]] \
            && [Term::get_line 1] == $line} {
        # We scrolled successfully.
+       pass "$testname (scroll cnt: $down_count)"
+       Term::dump_screen
     } else {
+       verbose -log "\n"
+       verbose -log "wait_for  : '$line'"
+       verbose -log "first line: '[Term::get_line 1]'"
        fail "$testname (scroll failed)"
        Term::dump_screen
        break
...
we can see what goes wrong.

We get:
...
wait_for  : '|    0x6b5                               data16 cs nopw
0x0(%rax,%rax,1)       |\
'
first line: '|    0x6b5                       data16 cs nopw 0x0(%rax,%rax,1)  
            |\
'
...
So, AFAIU this is about indentation.

TUI's behaviour doesn't look wrong to me, so I guess it's a question of
updating the test-case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-02-06 22:25 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-19 16:34 [Bug tui/26922] New: FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll failed) vries at gcc dot gnu.org
2020-11-19 16:39 ` [Bug tui/26922] " vries at gcc dot gnu.org
2020-11-19 16:39 ` vries at gcc dot gnu.org
2020-11-26 13:52 ` vries at gcc dot gnu.org
2021-02-05 16:31 ` vries at gcc dot gnu.org
2021-02-06 22:22 ` cvs-commit at gcc dot gnu.org
2021-02-06 22:25 ` [Bug testsuite/26922] " vries at gcc dot gnu.org

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