public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "csapuntz at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/15454] New: unusably slow resolving type names in C++ program with multiple namespace / lots of base classes Date: Fri, 10 May 2013 05:08:00 -0000 [thread overview] Message-ID: <bug-15454-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15454 Bug #: 15454 Summary: unusably slow resolving type names in C++ program with multiple namespace / lots of base classes Product: gdb Version: 7.6 Status: NEW Severity: critical Priority: P2 Component: c++ AssignedTo: unassigned@sourceware.org ReportedBy: csapuntz@gmail.com Classification: Unclassified Created attachment 7020 --> http://sourceware.org/bugzilla/attachment.cgi?id=7020 breakpoint trace It takes minutes for GDB to find a symbol (vol::content_lh_key in this case) defined in a global namespace unless I prefix the symbol with :: It seems to search for vol in the namespaces of all classes that the current class inherits from. This is ok, but it seems to repeat the search on the same symbol many times over. I ran gdb against gdb and capture a bunch of stack traces during the symbol lookup. The file is attached. break cp_lookup_symbol_in_namespace silent bt 4 print "\n\n" cont end -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-05-10 5:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-10 5:08 csapuntz at gmail dot com [this message] 2013-05-10 5:49 ` [Bug c++/15454] " csapuntz at gmail dot com 2013-06-05 20:09 ` keiths at redhat dot com 2014-01-25 21:04 ` altsysrq at gmail dot com
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-15454-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: 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).