public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: add debug prints in buildsym.c
Date: Sat, 30 Jul 2022 00:55:14 +0000 (GMT)	[thread overview]
Message-ID: <20220730005514.7BD26384B833@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=80affb9f80d22ee4b1463f23a36b083e05b6d2c3

commit 80affb9f80d22ee4b1463f23a36b083e05b6d2c3
Author: Simon Marchi <simon.marchi@polymtl.ca>
Date:   Thu Apr 7 09:27:18 2022 -0400

    gdb: add debug prints in buildsym.c
    
    Add a few debug prints in buildsym.c that were helpful to me in writing
    this series.
    
    Change-Id: If10a818feaee3ce1b78a2a254013b62dd578002b

Diff:
---
 gdb/buildsym.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gdb/buildsym.c b/gdb/buildsym.c
index 65c2ac5aff0..fae3d5ef4ce 100644
--- a/gdb/buildsym.c
+++ b/gdb/buildsym.c
@@ -493,6 +493,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;
@@ -513,6 +515,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;
 	}
@@ -741,6 +745,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;


                 reply	other threads:[~2022-07-30  0:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220730005514.7BD26384B833@sourceware.org \
    --to=simark@sourceware.org \
    --cc=gdb-cvs@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).