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] New: Setting a breakpoint in a C++ header file takes a long time
Date: Wed, 29 Nov 2023 12:27:11 +0000	[thread overview]
Message-ID: <bug-31095-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31095
           Summary: Setting a breakpoint in a C++ header file takes a long
                    time
           Product: gdb
           Version: 13.1
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: thomas at mitterfellner dot at
  Target Milestone: ---

I noticed that setting a breakpoint in a C++ header file (e.g. for a method
that only performs member initialization) using gdb 13.2 takes quite a long
time (>30 s). The project I experienced this in has ~800 cpp and ~1000 hpp
files.
Setting a breakpoint in a cpp file, on the other hand, is performed with no
noticable delay.

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

             reply	other threads:[~2023-11-29 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 12:27 thomas at mitterfellner dot at [this message]
2023-11-29 16:43 ` [Bug breakpoints/31095] " simark at simark dot ca
2023-11-29 17:51 ` thomas at mitterfellner dot at
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@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).