public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/26922] FAIL: gdb.tui/tui-layout-asm.exp: scroll to end of assembler (scroll failed)
Date: Thu, 26 Nov 2020 13:52:27 +0000	[thread overview]
Message-ID: <bug-26922-4717-cXINalOHZH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26922-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Another occurrence, now without -PIE.

Before:
...
    0
+------------------------------------------------------------------------------+
    1 |    0x4005d9 <__libc_csu_init+89>   call   *(%r15,%rbx,8)               
     |
    2 |    0x4005dd <__libc_csu_init+93>   add    $0x1,%rbx                    
     |
    3 |    0x4005e1 <__libc_csu_init+97>   cmp    %rbp,%rbx                    
     |
    4 |    0x4005e4 <__libc_csu_init+100>  jb     0x4005d0 <__libc_csu_init+80>
     |
    5 |    0x4005e6 <__libc_csu_init+102>  mov    0x8(%rsp),%rbx               
     |
    6 |    0x4005eb <__libc_csu_init+107>  mov    0x10(%rsp),%rbp              
     |
    7 |    0x4005f0 <__libc_csu_init+112>  mov    0x18(%rsp),%r12              
     |
    8 |    0x4005f5 <__libc_csu_init+117>  mov    0x20(%rsp),%r13              
     |
    9 |    0x4005fa <__libc_csu_init+122>  mov    0x28(%rsp),%r14              
     |
   10 |    0x4005ff <__libc_csu_init+127>  mov    0x30(%rsp),%r15              
     |
   11 |    0x400604 <__libc_csu_init+132>  add    $0x38,%rsp                   
     |
   12 |    0x400608 <__libc_csu_init+136>  ret                                 
     |
   13 |    0x400609                            nopl   0x0(%rax)                
     |
   14
+------------------------------------------------------------------------------+
...

After:
...
    0
+------------------------------------------------------------------------------+
    1 |    0x4005dd <__libc_csu_init+93>           add    $0x1,%rbx            
     |
    2 |    0x4005e1 <__libc_csu_init+97>           cmp    %rbp,%rbx            
     |
    3 |    0x4005e4 <__libc_csu_init+100>          jb     0x4005d0
<__libc_csu_init+8|
    4 |    0x4005e6 <__libc_csu_init+102>          mov    0x8(%rsp),%rbx       
     |
    5 |    0x4005eb <__libc_csu_init+107>          mov    0x10(%rsp),%rbp      
     |
    6 |    0x4005f0 <__libc_csu_init+112>          mov    0x18(%rsp),%r12      
     |
    7 |    0x4005f5 <__libc_csu_init+117>          mov    0x20(%rsp),%r13      
     |
    8 |    0x4005fa <__libc_csu_init+122>          mov    0x28(%rsp),%r14      
     |
    9 |    0x4005ff <__libc_csu_init+127>          mov    0x30(%rsp),%r15      
     |
   10 |    0x400604 <__libc_csu_init+132>          add    $0x38,%rsp           
     |
   11 |    0x400608 <__libc_csu_init+136>          ret                         
     |
   12 |    0x400609                                    nopl   0x0(%rax)        
     |
   13 |    0x400610 <__do_global_ctors_aux>        push   %rbp                 
     |
   14
+------------------------------------------------------------------------------+
...

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

  parent reply	other threads:[~2020-11-26 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 16:34 [Bug tui/26922] New: " 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 [this message]
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

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=bug-26922-4717-cXINalOHZH@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).