From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 2/7] gdb: add debug prints in buildsym.c
Date: Wed, 27 Apr 2022 23:35:37 -0400 [thread overview]
Message-ID: <20220428033542.1636284-3-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20220428033542.1636284-1-simon.marchi@polymtl.ca>
Add a few debug prints in buildsym.c that were helpful to me in writing
this series.
Change-Id: If10a818feaee3ce1b78a2a254013b62dd578002b
---
gdb/buildsym.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/gdb/buildsym.c b/gdb/buildsym.c
index c54e6586cedb..feef5038773f 100644
--- a/gdb/buildsym.c
+++ b/gdb/buildsym.c
@@ -496,6 +496,8 @@ buildsym_compunit::start_subfile (const char *name)
{
/* See if this subfile is already registered. */
+ symtab_create_debug_printf ("name = %s", name);
+
for (subfile *subfile = m_subfiles; subfile; subfile = subfile->next)
{
std::string subfile_name_holder;
@@ -516,6 +518,8 @@ buildsym_compunit::start_subfile (const char *name)
if (FILENAME_CMP (subfile_name, name) == 0)
{
+ symtab_create_debug_printf ("found existing symtab with name %s (%s)",
+ subfile->name.c_str (), subfile_name);
m_current_subfile = subfile;
return;
}
@@ -744,6 +748,9 @@ buildsym_compunit::watch_main_source_file_lossage ()
Copy its line_vector and symtab to the main subfile
and then discard it. */
+ symtab_create_debug_printf ("using subfile %s as the main subfile",
+ mainsub_alias->name.c_str ());
+
mainsub->line_vector_entries
= std::move (mainsub_alias->line_vector_entries);
mainsub->symtab = mainsub_alias->symtab;
--
2.35.2
next prev parent reply other threads:[~2022-04-28 3:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 3:35 [PATCH v3 0/7] Fix printing macros Simon Marchi
2022-04-28 3:35 ` [PATCH v3 1/7] gdb: introduce symtab_create_debug_printf Simon Marchi
2022-04-28 15:49 ` Tom Tromey
2022-04-28 3:35 ` Simon Marchi [this message]
2022-04-28 15:50 ` [PATCH v3 2/7] gdb: add debug prints in buildsym.c Tom Tromey
2022-04-28 3:35 ` [PATCH v3 3/7] gdb/dwarf: pass compilation directory to line header Simon Marchi
2022-04-28 15:48 ` Tom Tromey
2022-04-28 15:59 ` Simon Marchi
2022-04-28 3:35 ` [PATCH v3 4/7] gdb/dwarf: pass a file_entry to line_header::file_file_name Simon Marchi
2022-05-03 20:12 ` Bruno Larsen
2022-07-28 16:26 ` Simon Marchi
2022-04-28 3:35 ` [PATCH v3 5/7] gdb: add "id" fields to identify symtabs and subfiles Simon Marchi
2022-04-28 23:53 ` Lancelot SIX
2022-07-28 17:46 ` Simon Marchi
2022-04-28 3:35 ` [PATCH v3 6/7] gdb: remove code to prepend comp dir in buildsym_compunit::start_subfile Simon Marchi
2022-05-12 13:07 ` Bruno Larsen
2022-07-28 17:47 ` Simon Marchi
2022-04-28 3:35 ` [PATCH v3 7/7] gdb/testsuite: add macros test for source files compiled in various ways Simon Marchi
2022-05-12 13:17 ` Bruno Larsen
2022-07-28 17:51 ` Simon Marchi
2022-07-30 0:56 ` [PATCH v3 0/7] Fix printing macros Simon Marchi
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=20220428033542.1636284-3-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).