Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org,
	Simon Marchi <simon.marchi@ericsson.com>,
	       Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH v2] linux: Add maintenance commands to test libthread_db
Date: Thu, 24 May 2018 14:10:00 -0000	[thread overview]
Message-ID: <24cc63299f03c8616f081466041e9321@polymtl.ca> (raw)
In-Reply-To: <1527096776-29187-1-git-send-email-gbenson@redhat.com>

On 2018-05-23 13:32, Gary Benson wrote:
> Hi all,
> 
> This is an updated version of a patch I submitted for review back in
> November.  It adds two new commands which may be used to test thread
> debugging libraries used by GDB:
> 
>   * "maint check libthread-db" tests the thread debugging library GDB
>      is using for the current inferior.
> 
>   * "maint set/show check-libthread-db" selects whether libthread_db
>      tests should be run automatically as libthread_db is auto-loaded.
>      The default is to not run tests automatically.
> 
> 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.
> 
> GDB changes since version 1:
>  - The check no longer requires debuginfo for glibc.  [Simon]
>  - Parts of the check are skipped when working with core files.
>    (I hadn't checked this until Pedro asked about them).
>    Previously the check would fail because one of the tested
>    operations does not work with core files on some platforms.
>  - Macros starting with double underscores have been renamed.  [Pedro]
>    (The macros have been somewhat reorganized too, to implement
>    the core files change I mentioned above).
>  - libthread_db_debug now is treated as a boolean in the place
>    where previously it wasn't.  [Simon]
>  - There is a NEWS entry. [Pedro]
> 
> Testcase changes since version 1:
>  - Test names no longer contain parentheses.  [Simon]
>  - The criteria for skipping the test have been replaced with
>    Pedro's suggestion.  [Pedro]
>  - Numbers in testcase comments have been removed.  [Pedro]
> 
> Built and regtested on RHEL 7.5 x86_64.
> 
> Ok to commit?
> 
> Thanks,
> Gary

The patch looks good from my side.

Simon


  parent reply	other threads:[~2018-05-24 12:53 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
2018-06-05 15:46     ` Gary Benson
2018-06-05 16:11       ` Eli Zaretskii
2018-05-24 14:10   ` Simon Marchi [this message]
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=24cc63299f03c8616f081466041e9321@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --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