public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dmitry.neverov at jetbrains dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30520] Slow lookup_symbol_in_objfile Date: Wed, 07 Jun 2023 09:50:50 +0000 [thread overview] Message-ID: <bug-30520-4717-L9IjCp54P2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30520-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30520 --- Comment #4 from Dmitry Neverov <dmitry.neverov at jetbrains dot com> --- With 'set debug symtab-create 1' gdb produces ~450Mb of logs between these 2 entries: 2023-06-06 10:54:51,286 <&" [symbol-lookup] lookup_symbol_in_objfile: lookup_symbol_in_objfile (_pcbnew.kiface, GLOBAL_BLOCK, wxObjectDataPtr, VAR_DOMAIN)\n" 2023-06-06 10:55:50,418 <&" [symbol-lookup] lookup_symbol_in_objfile: lookup_symbol_in_objfile (...) = NULL\n" All log entries are of the form like these: <&" [symtab-create] start_subfile: name = /usr/include/x86_64-linux-gnu/c++/12/bits/c++config.h, name_for_id = /usr/include/x86_64-linux-gnu/c++/12/bits/c++config.h\n" <&" [symtab-create] start_subfile: found existing symtab with name_for_id /usr/include/x86_64-linux-gnu/c++/12/bits/c++config.h\n" There are 1134332 '[symtab-create] start_subfile: name = ...' entries total, 707543 of them result in 'found existing symtab', 426789 don't find an existing symtab. There are 3519 unique names for symtab-create. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-07 9:50 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-06 9:52 [Bug symtab/30520] New: " dmitry.neverov at jetbrains dot com 2023-06-06 11:39 ` [Bug symtab/30520] " dmitry.neverov at jetbrains dot com 2023-06-06 11:41 ` dmitry.neverov at jetbrains dot com 2023-06-06 19:51 ` tromey at sourceware dot org 2023-06-07 8:38 ` sam at gentoo dot org 2023-06-07 9:50 ` dmitry.neverov at jetbrains dot com [this message] 2023-06-09 8:52 ` dmitry.neverov at jetbrains dot com 2023-11-06 10:45 ` dmitry.neverov at jetbrains dot com 2023-11-30 17:07 ` tromey at sourceware dot org 2023-12-01 20:28 ` tromey at sourceware dot org 2024-01-19 16:52 ` tromey at sourceware dot org 2024-01-20 8:36 ` sam at gentoo dot org 2024-01-30 11:51 ` josh.cottingham at linaro dot org 2024-01-30 11:52 ` josh.cottingham at linaro dot org 2024-02-15 17:02 ` tromey at sourceware dot org 2024-02-15 17:05 ` tromey at sourceware dot org 2024-05-10 22:06 ` brobecker at gnat dot com 2024-05-17 14:49 ` cvs-commit at gcc dot gnu.org 2024-05-17 14:50 ` tromey at sourceware dot org
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-30520-4717-L9IjCp54P2@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).