From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DECC03864858; Wed, 17 Mar 2021 10:55:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DECC03864858 From: "edd at theunixzoo dot co.uk" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: edd at theunixzoo dot co.uk X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 10:55:33 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27593 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=