Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
	roland@redhat.com
Subject: Re: [patch] Fix for 'too much spew with "set verbose on"'
Date: Fri, 30 Jul 2010 22:14:00 -0000	[thread overview]
Message-ID: <201007302314.26917.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTimRceDgkDt88ZybuEdGYAPZq_=6dkEknP0yRaKU@mail.gmail.com>

On Friday 30 July 2010 22:52:15, Paul Pluzhnikov wrote:
> On Fri, Jul 30, 2010 at 11:18 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> 
> > set debug libthread-db
> 
> Good idea.  Revised patch attached.

Thanks.

> 2010-07-30  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
>        * linux-thread-db.c (libthread_db_debug): New variable.
>        (thread_db_find_new_threads_silently): Control verbosity with it.
>        (try_thread_db_load_1, try_thread_db_load): Likewise.
>        (find_new_threads_once): Likewise.
>        (_initialize_thread_db): Set/show it.

This is okay.  Please wait for Eli to comment on the new
docs / help strings.

> doc/ChangeLog:
> 
> 2010-07-30  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
>        * gdb.texinfo (Threads): Document 'debug libthread-db'.

> +static void
> +show_libthread_db_debug (struct ui_file *file, int from_tty,
> +                        struct cmd_list_element *c, const char *value)
> +{
> +  fprintf_filtered (file, _("libhtread-db debugging is %s.\n"), value);

Typo, "libthread-db".

-- 
Pedro Alves


  reply	other threads:[~2010-07-30 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinY+o2nw0Ld5dq5Grkd05Oyc+ZTiDE=7N0XdDj_@mail.gmail.com>
2010-07-30 18:09 ` Eli Zaretskii
2010-07-30 18:18   ` Pedro Alves
2010-07-30 21:52     ` Paul Pluzhnikov
2010-07-30 22:14       ` Pedro Alves [this message]
2010-07-31  7:10       ` Eli Zaretskii
2010-07-31 15:41         ` Paul Pluzhnikov

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=201007302314.26917.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.com \
    --cc=roland@redhat.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