Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 0/8] Demangle minimal symbol names in worker threads
Date: Wed, 29 May 2019 21:29:00 -0000	[thread overview]
Message-ID: <20190529212916.23721-1-tom@tromey.com> (raw)

This is v3 of my patch series to demangle minimal symbol names in
worker threads.

v2 was here:

    https://sourceware.org/ml/gdb-patches/2019-05/msg00448.html

This version adds control over the maximum number of threads to use,
and attempts to address the documentation review comments.

Tom



             reply	other threads:[~2019-05-29 21:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 21:29 Tom Tromey [this message]
2019-05-29 21:29 ` [PATCH v3 1/8] Defer minimal symbol name-setting Tom Tromey
2019-05-29 21:29 ` [PATCH v3 3/8] Add configure check for std::thread Tom Tromey
2019-05-30 11:34   ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 4/8] Lock the demangled hash table Tom Tromey
2019-05-30 12:58   ` Pedro Alves
2019-05-30 14:03     ` Pedro Alves
2019-05-30 21:58     ` Tom Tromey
2019-05-29 21:29 ` [PATCH v3 2/8] Remove static buffer from ada_decode Tom Tromey
2019-05-30  0:08   ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 5/8] Introduce run_on_main_thread Tom Tromey
2019-05-30 13:12   ` Pedro Alves
2019-05-30 13:20     ` Tom Tromey
2019-05-30 13:57       ` Pedro Alves
2019-05-30 14:01       ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 8/8] Add maint set/show max-worker-threads Tom Tromey
2019-05-30  2:36   ` Eli Zaretskii
2019-05-30 14:20   ` Pedro Alves
2019-05-29 21:29 ` [PATCH v3 7/8] Demangle minsyms in parallel Tom Tromey
2019-05-30 14:19   ` Pedro Alves
2019-05-30 22:22     ` Tom Tromey
2019-05-29 22:03 ` [PATCH v3 6/8] Introduce thread-safe way to handle SIGSEGV Tom Tromey
2019-05-30 13:40   ` Pedro Alves
2019-06-09 15:43     ` 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=20190529212916.23721-1-tom@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    /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