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: Mon, 06 Nov 2023 10:45:08 +0000	[thread overview]
Message-ID: <bug-30520-4717-OelsTCC4qI@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 #6 from Dmitry Neverov <dmitry.neverov at jetbrains dot com> ---
I investigated it a bit further and the slowness seems to be
indeed caused by too much symtab expansion:

https://sourceware.org/pipermail/gdb/2023-October/050976.html

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

  parent reply	other threads:[~2023-11-06 10:45 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
2023-06-09  8:52 ` dmitry.neverov at jetbrains dot com
2023-11-06 10:45 ` dmitry.neverov at jetbrains dot com [this message]
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-OelsTCC4qI@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).