From: Eli Zaretskii <eliz@gnu.org>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org, simon.marchi@ericsson.com, palves@redhat.com
Subject: Re: [PATCH v2] linux: Add maintenance commands to test libthread_db
Date: Wed, 23 May 2018 19:21:00 -0000 [thread overview]
Message-ID: <837enuclmj.fsf@gnu.org> (raw)
In-Reply-To: <1527096776-29187-1-git-send-email-gbenson@redhat.com> (message from Gary Benson on Wed, 23 May 2018 18:32:56 +0100)
> From: Gary Benson <gbenson@redhat.com>
> Cc: Simon Marchi <simon.marchi@ericsson.com>, Pedro Alves <palves@redhat.com>
> Date: Wed, 23 May 2018 18:32:56 +0100
>
> The test itself is a basic integrity check exercising all libthread_db
> functions used by GDB on GNU/Linux systems. By extension this also
> exercises the proc_service functions provided by GDB that libthread_db
> uses. This is useful for NPTL developers and libthread_db developers.
> It could also prove useful investigating bugs reported against GDB
> where the thread debugging library or GDB's proc_service layer is
> suspect.
I think some of this text should be in the manual, otherwise the
description of the command is not very useful.
> diff --git a/gdb/NEWS b/gdb/NEWS
> index cef5580..2e6cb74 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -27,6 +27,16 @@ set|show record btrace cpu
> Controls the processor to be used for enabling errata workarounds for
> branch trace decode.
>
> +maint check libthread-db
> + Run integrity checks on the current inferior's thread debugging
> + library
> +
> +maint set check-libthread-db (on|off)
> +maint show check-libthread-db
> + Control whether to run integrity checks on inferior specific thread
> + debugging libraries as they are loaded. The default is not to
> + perform such checks.
> +
> * Python API
This part is OK.
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 28f083f..6faaabe 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -35533,6 +35533,11 @@ modify XML target descriptions.
> Check that the target descriptions dynamically created by @value{GDBN}
> equal the descriptions created from XML files found in @var{dir}.
>
> +@kindex maint check libthread-db
> +@item maint check libthread-db
> +Run integrity checks on the current inferior's thread debugging
> +library.
> +
> @kindex maint print dummy-frames
> @item maint print dummy-frames
> Prints the contents of @value{GDBN}'s internal dummy-frame stack.
> @@ -35840,6 +35845,14 @@ number of blocks in the blockvector
> @end enumerate
> @end table
>
> +@kindex maint set check-libthread-db
> +@kindex maint show check-libthread-db
> +@item maint set check-libthread-db [on|off]
> +@itemx maint show check-libthread-db
> +Control whether @value{GDBN} should run integrity checks on inferior
> +specific thread debugging libraries as they are loaded. The default
> +is not to perform such checks.
> +
This is also OK, modulo the request to expand the description.
Thanks.
next prev parent reply other threads:[~2018-05-23 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 14:42 [PATCH] " Gary Benson
2017-11-22 19:31 ` Simon Marchi
2017-11-23 13:22 ` Pedro Alves
2018-05-23 18:57 ` [PATCH v2] " Gary Benson
2018-05-23 19:21 ` Eli Zaretskii [this message]
2018-06-05 15:46 ` Gary Benson
2018-06-05 16:11 ` Eli Zaretskii
2018-05-24 14:10 ` Simon Marchi
2018-06-05 16:31 ` Pedro Alves
2018-06-08 17:25 ` [PATCH v3/pushed] " Gary Benson
2018-06-11 17:15 ` [PATCH] Fix ref in gdb.texinfo Szabolcs Nagy
2018-06-11 17:32 ` Eli Zaretskii
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=837enuclmj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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