From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 77F72385841F; Wed, 29 Nov 2023 17:51:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 77F72385841F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1701280269; bh=AFAd6Pf5wLY1HBueYGm5CA3wpW2CLCUQj8xRI1qsF28=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OdlkD1/XIxojy+ReiMWWpNurmYSKGlzJaAIuXejEUZ8QtQUam1F7GtJb/IpeWlW4L ibPQUMkflCGKJr8wEKncYitjebo7C6FPMypN+wJw7FjcA37DIcBrZap1pkcbklye/e eHAfjgoFMUefB5CSbgBVIXttHqUJSPM3Xn1yHGo0= From: "thomas at mitterfellner dot at" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/31095] Setting a breakpoint in a C++ header file takes a long time Date: Wed, 29 Nov 2023 17:51:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: thomas at mitterfellner dot at 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: 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=3D31095 --- Comment #2 from Thomas --- I know I've experienced this behavior in versions prior to 13 2 (definitely in 13.1 too). I've been setting the breakpoints in VS Code (usually many of them, most in= cpp files, though, so it wasn't obvious to me that the breakpoints in the header files are causing the delay). When I actually start the debugging session, I see in the console that gdb starts quickly but then it takes a long time for the program to be debugged to start (the breakpoints in the main routine to= be reached). When I had found out the cause of the delay by chance, I tried this from a command line gdb session. At the prompt, I set a breakpoint via b file.hpp: and as soon as I hit Enter, there's a delay before I get the next prompt. I cross-checked in a new session; when I do b file.cpp: and hit Enter, I immediately get a new prompt. Regarding the number of files the headers are included from: I have to check that separately (but I think it's not too many). --=20 You are receiving this mail because: You are on the CC list for the bug.=