Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	jhb@freebsd.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add "set debug minsyms" command
Date: Wed, 26 Dec 2018 16:43:00 -0000	[thread overview]
Message-ID: <9e2735708c805257c37485fbc2f451a8@polymtl.ca> (raw)
In-Reply-To: <878t0er6l6.fsf@tromey.com>

On 2018-12-24 15:51, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
> 
> Simon> It was indeed missing from the original patch, but I ended up 
> not
> Simon> adding a new command, so I don't think this is needed.
> 
> The manual documents the values for "set debug symtab-create".  I think
> a patch is indeed needed since you added a new value.

Actually that value is already used and documented:

Turns on or off display of debugging messages related to symbol table 
creation. The default is 0 (off). A value of 1 provides basic 
information. A value greater than 1 provides more verbose information.

> Also I was wondering why not just use "maint print msymbols".

Because I didn't know about it :).  Do you think the new debugging 
output is redundant and should be removed?  It's the same data (minimal 
symbols), but in a different order.  With "set debug symtab-create", 
they are shown in the order they are provided by the symbol reader (same 
order as in the file usually), whereas "maint print msymbols" shows them 
as saved in GDB's memory, sorted by address.  I think that the "set 
debug symtab-create" may be useful when debugging the symbol reader, 
whereas "maint print msymbols" may be useful when debugging lookups.

Simon


  reply	other threads:[~2018-12-26 16:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181221214706.26981-1-simon.marchi@ericsson.com>
2018-12-21 21:59 ` John Baldwin
2018-12-21 23:07   ` Simon Marchi
     [not found]     ` <798386c1-43f5-862e-1ee4-6e439ccf3133@FreeBSD.org>
2018-12-22  2:20       ` Simon Marchi
2018-12-22  7:29         ` Eli Zaretskii
2018-12-22 15:17           ` Simon Marchi
2018-12-24 20:51             ` Tom Tromey
2018-12-26 16:43               ` Simon Marchi [this message]
2018-12-26 17:19                 ` Eli Zaretskii
2018-12-26 17:24                   ` Simon Marchi
2018-12-26 18:48                     ` Eli Zaretskii
2018-12-29 18:55                 ` Tom Tromey

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=9e2735708c805257c37485fbc2f451a8@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.org \
    --cc=tom@tromey.com \
    /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