public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "thomas at mitterfellner dot at" <sourceware-bugzilla@sourceware.org> 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 [thread overview] Message-ID: <bug-31095-4717-HcjtxUmOkT@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31095-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31095 --- Comment #2 from Thomas <thomas at mitterfellner dot at> --- 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:<line no.> 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:<line no.> 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). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-29 17:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-29 12:27 [Bug breakpoints/31095] New: " thomas at mitterfellner dot at 2023-11-29 16:43 ` [Bug breakpoints/31095] " simark at simark dot ca 2023-11-29 17:51 ` thomas at mitterfellner dot at [this message] 2023-11-29 19:18 ` simark at simark dot ca 2023-11-29 19:57 ` thomas at mitterfellner dot at 2023-11-30 17:00 ` tromey at sourceware dot org 2023-12-11 15:35 ` thomas at mitterfellner dot at
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-31095-4717-HcjtxUmOkT@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: linkBe 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).