From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 022F83858D38; Fri, 10 Nov 2023 18:29:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 022F83858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1699640991; bh=QcPmSagOC7+rq5FiXtjJFJW5grZU5TBHLVmGFYMd4GY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xjAllXCCxiHpTf3aFidKp/kiSlh9wXy5suj9Y4yJw7VlNheYiZEGngNHn4e8UygDB 4A44f4M1VMdwbM6CMRJ2mVaBfG8OdQPp8bAHUBMJr3jtww6krUtZv2x2QjBmbsmfi6 92VqVw8bh6frFPp8icrMnoLM0G6CgGLk8ao5SZAw= From: "simon.marchi at polymtl dot ca" To: gdb-prs@sourceware.org Subject: [Bug gdb/31048] GDB commands very slow due to too many lseek calls Date: Fri, 10 Nov 2023 18:29:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at polymtl dot ca 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: cc Message-ID: In-Reply-To: References: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31048 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at polymtl do= t ca --- Comment #3 from Simon Marchi --- Hi Aditya, First of all, can you try with GDB from the git master branch? It is not really useful to develop on an old version like 9.2, since what you find mi= ght not apply to the current code. Then, do you think you would be able to make a reproducer? Otherwise all we can do is speculate, and that is not really useful. Otherwise, I would suggest giving profiling a shot to see where time is spe= nt.=20 I personally use `perf` for that. --=20 You are receiving this mail because: You are on the CC list for the bug.=