public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Dmitry Neverov <dmitry.neverov@jetbrains.com>
To: gdb@sourceware.org
Subject: Index files are not used in the session where they were created
Date: Tue, 25 Jul 2023 10:01:49 +0200	[thread overview]
Message-ID: <CAEY59_KmafbXkjSVk1kp-dFxp6RA3Srs2aUPu6a-euXtbM-Buw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

I'm investigating whether index-caches help with slow symbols
loading (https://sourceware.org/bugzilla/show_bug.cgi?id=30520).

They seem to help, but only on the second gdb run. When I start a
debug session for the first time with an empty ~/.caches/gdb
directory, I can see from logs that gdb tries to read index
files, fails because they don't exist, and then writes index to
disk. The index is saved in a few seconds.

If I then try loading children of a variable causing a slow symbol
lookup, the lookup is still slow. Even though the index is ready
and is saved to disk.

If I restart gdb after the index is written, then gdb picks it
up, and symbol loading is much faster - a few seconds instead of
a minute.

Is there a way to use the created index without gdb restart?

-- 
Dmitrii Neverov

             reply	other threads:[~2023-07-25  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  8:01 Dmitry Neverov [this message]
2023-07-26 16:20 ` Tom Tromey
2023-08-01  6:42   ` Dmitry Neverov
2023-10-13  8:57     ` Dmitry Neverov
2023-10-25 15:59       ` Dmitry Neverov
2023-11-01 17:51         ` Tom Tromey
2023-11-06 10:41           ` Dmitry Neverov
2023-11-13 16:59           ` Dmitry Neverov
2023-11-15 10:18           ` Dmitry Neverov

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=CAEY59_KmafbXkjSVk1kp-dFxp6RA3Srs2aUPu6a-euXtbM-Buw@mail.gmail.com \
    --to=dmitry.neverov@jetbrains.com \
    --cc=gdb@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).