public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: too much spew with "set verbose on"
Date: Mon, 28 Jun 2010 18:16:00 -0000	[thread overview]
Message-ID: <20100628181607.22EF449A4F@magilla.sf.frob.com> (raw)
In-Reply-To: Paul Pluzhnikov's message of  Sunday, 27 June 2010 08:24:23 -0700 <AANLkTil7gnpncc6LDl2aYfo_O2gzfMt1XygWFY-qpTMt@mail.gmail.com>

> GDB is telling you what it is doing, so yes, it should be saying all
> this because that's exactly what it is doing.

Nonsense.  GDB is doing a thousand things it doesn't print about.
Plain "set verbose" is a normal user command for normal users, not
just for people interested in all manner of GDB internals.

"Symbols already loaded for ..." is not something GDB is doing.
It's something GDB is *not* doing.  But anyway, mostly I was referring
to the repetition of various identical messages more than once for
a single "run" command.

> We could perhaps move some of this output under separate "maintenance
> set verbose" flag, or perhaps "set print symbol-events" and "set print
> libthread_db-events" or some such.

The libthread_db events should certainly go into some maint subcommand.
I'm the libthread_db maintainer, and I don't want to see those!


Thanks,
Roland

      parent reply	other threads:[~2010-06-28 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 19:25 Roland McGrath
     [not found] ` <AANLkTil7gnpncc6LDl2aYfo_O2gzfMt1XygWFY-qpTMt@mail.gmail.com>
2010-06-28 18:16   ` Roland McGrath [this message]

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=20100628181607.22EF449A4F@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=ppluzhnikov@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).