From: Pedro Alves <palves@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [FYI/PUSHED] Revert "Turn off threaded minsym demangling by default"
Date: Mon, 16 Dec 2019 19:17:00 -0000 [thread overview]
Message-ID: <8f4bcf24-abd0-90fd-b20e-38f6feb2dfa6@redhat.com> (raw)
In-Reply-To: <CAPTJ0XEiPLTaOjBvsS2jegqgFYADVdkrTSL2+TFr69K=kTOW+Q@mail.gmail.com>
On 12/14/19 6:23 PM, Christian Biesinger via gdb-patches wrote:
> On Fri, Dec 13, 2019 at 6:16 PM Tom Tromey <tom@tromey.com> wrote:
>>
>>>>>>> ">" == cbiesinger <cbiesinger@chromium.org> writes:
>>
>>>> As agreed on the mailing list, now that GDB 9 has branched, this patch
>>>> reverts the change to set worker-threads to zero. After this patch,
>>>> multithreaded minsym demangling will be enabled again by default.
>>
>> Thanks. I think maybe the docs needed a tweak as well?
>
> I only changed the NEWS entry that mentioned the default value. I was
> wondering about that -- should I change that to say the default is now
> back to unlimited or no?
There should be a new entry in the "Changes since GDB 9" section,
talking about multhreaded debugging now being enabled by default.
The "Changes in GDB 9" entry should remain the same as it was in
GDB 9, since that's how GDB 9 behaved.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-12-16 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 22:45 cbiesinger
2019-12-13 23:16 ` Tom Tromey
2019-12-14 18:23 ` Christian Biesinger via gdb-patches
2019-12-16 19:17 ` Pedro Alves [this message]
2019-12-20 0:25 ` Christian Biesinger via gdb-patches
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=8f4bcf24-abd0-90fd-b20e-38f6feb2dfa6@redhat.com \
--to=palves@redhat.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).