public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "edd at theunixzoo dot co.uk" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27593] New: Scrolling up can be extremely slow.
Date: Wed, 17 Mar 2021 10:55:32 +0000	[thread overview]
Message-ID: <bug-27593-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27593
           Summary: Scrolling up can be extremely slow.
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: edd at theunixzoo dot co.uk
  Target Milestone: ---

It seems that Bug #26024 (Cannot scroll up in asm view) has now been fixed, but
I notice that there are scenarios where scrolling up is extremely slow.

I have an 85MB crashing Rust binary here. If I run it to the crash the
backtrace is:
```
Thread 1 "tests-014a21cc2" received signal SIGABRT, Aborted.
0x00007ffff7b367bb in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff7b367bb in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff7b21535 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007ffff7b78508 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00007ffff7b7ec1a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007ffff7b7f184 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x00005555557c7151 in ?? ()
#6  0x00005555557c6cc4 in ?? ()
#7  0x00005555557c63f1 in ?? ()
#8  0x00005555557c2987 in ?? ()
#9  0x00005555557d62d3 in ?? ()
#10 0x00005555557c0f33 in ?? ()
#11 0x00005555557c1182 in ?? ()
#12 0x00005555557bee09 in tests::main () at
/home/vext01/research/yorick/yk/tests/src/lib.rs:1
```

Switching to asm layout in the top frame (#0), scroll up works well.

Moving down the stack, #1 through #4 all scroll up fine too.

In #5 however, scrolling up one line:
  - Takes about 20 seconds.
  - Causes one CPU core to be pegged at 100% during this time.
  - Blocks the GDB TUI in the meantime.

The same happens for #6 through #12 (inclusive).

I had postured that, gdb has to do some kind of search when the file for a
frame's code is unknown, but #12 being slow to scroll disproves this.

This occurs on gdb-10.1 and the current (as of today) git code.

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

             reply	other threads:[~2021-03-17 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 10:55 edd at theunixzoo dot co.uk [this message]
2021-03-17 10:58 ` [Bug gdb/27593] " edd at theunixzoo dot co.uk
2021-03-17 16:47 ` ssbssa at sourceware dot org
2021-03-17 16:58 ` edd at theunixzoo dot co.uk
2021-03-17 17:21 ` ssbssa at sourceware dot org
2022-03-06 17:34 ` [Bug tui/27593] " tromey at sourceware dot 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-27593-4717@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).