From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 3/4] [gdb/cli] Keep track of styling failures in source_cache
Date: Fri, 13 Oct 2023 14:19:52 +0200 [thread overview]
Message-ID: <20231013121953.25917-4-tdevries@suse.de> (raw)
In-Reply-To: <20231013121953.25917-1-tdevries@suse.de>
In source_cache::ensure, keep track of which files failed to be styled, and
don't attempt to style them again in case the file dropped out of the cache.
Tested on x86_64-linux.
---
gdb/source-cache.c | 24 ++++++++++++++++++++++--
gdb/source-cache.h | 4 ++++
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/gdb/source-cache.c b/gdb/source-cache.c
index 9757721e932..f8c98d7e23f 100644
--- a/gdb/source-cache.c
+++ b/gdb/source-cache.c
@@ -285,7 +285,8 @@ source_cache::ensure (struct symtab *s)
return false;
}
- if (source_styling && gdb_stdout->can_emit_style_escape ())
+ if (source_styling && gdb_stdout->can_emit_style_escape ()
+ && m_no_styling_files.count (fullname) == 0)
{
bool already_styled
= try_source_highlight (contents, s->language (), fullname);
@@ -295,7 +296,26 @@ source_cache::ensure (struct symtab *s)
gdb::optional<std::string> ext_contents;
ext_contents = ext_lang_colorize (fullname, contents);
if (ext_contents.has_value ())
- contents = std::move (*ext_contents);
+ {
+ contents = std::move (*ext_contents);
+ already_styled = true;
+ }
+ }
+
+ if (!already_styled)
+ {
+ /* Styling failed. Styling can fail for instance for these
+ reasons:
+ - the language is not supported.
+ - the language cannot not be auto-detected from the file name.
+ - no stylers available.
+
+ Since styling failed, don't try styling the file again after it
+ drops from the cache.
+
+ Note that clearing the source cache also clears
+ m_no_styling_files. */
+ m_no_styling_files.insert (fullname);
}
}
diff --git a/gdb/source-cache.h b/gdb/source-cache.h
index bec6598ff9f..f1d30b43ce0 100644
--- a/gdb/source-cache.h
+++ b/gdb/source-cache.h
@@ -66,6 +66,7 @@ class source_cache
{
m_source_map.clear ();
m_offset_cache.clear ();
+ m_no_styling_files.clear ();
}
private:
@@ -95,6 +96,9 @@ class source_cache
/* The file offset cache. The key is the full name of the source
file. */
std::unordered_map<std::string, std::vector<off_t>> m_offset_cache;
+
+ /* The list of files where styling failed. */
+ std::unordered_set<std::string> m_no_styling_files;
};
/* The global source cache. */
--
2.35.3
next prev parent reply other threads:[~2023-10-13 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 12:19 [PATCH v2 0/4] [gdb/cli] Allow source highlighting to be interrupted Tom de Vries
2023-10-13 12:19 ` [PATCH v2 1/4] [gdb/cli] Skip string copy in source_cache::ensure Tom de Vries
2023-10-13 16:34 ` Lancelot SIX
2023-10-16 7:40 ` Tom de Vries
2023-10-13 12:19 ` [PATCH v2 2/4] [gdb/cli] Factor out try_source_highlight Tom de Vries
2023-10-13 16:52 ` Lancelot SIX
2023-10-16 7:07 ` Tom de Vries
2023-10-16 8:25 ` Lancelot SIX
2023-10-13 12:19 ` Tom de Vries [this message]
2023-10-13 12:19 ` [PATCH v2 4/4] [gdb/cli] Allow source highlighting to be interrupted Tom de Vries
2023-10-13 17:00 ` Lancelot SIX
2023-10-16 7:47 ` Tom de Vries
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=20231013121953.25917-4-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@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).