From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [FYI/PUSHED] Revert "Turn off threaded minsym demangling by default"
Date: Fri, 20 Dec 2019 00:25:00 -0000 [thread overview]
Message-ID: <CAPTJ0XGrLvf7pSOxfxKEHfmgRbxaV6KqLTb3mtMo1+8-vpncPA@mail.gmail.com> (raw)
In-Reply-To: <8f4bcf24-abd0-90fd-b20e-38f6feb2dfa6@redhat.com>
On Mon, Dec 16, 2019 at 1:17 PM Pedro Alves <palves@redhat.com> wrote:
>
> 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.
OK, I sent https://sourceware.org/ml/gdb-patches/2019-12/msg00843.html,
let me know what yall think.
Christian
prev parent reply other threads:[~2019-12-20 0:25 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
2019-12-20 0:25 ` Christian Biesinger via gdb-patches [this message]
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=CAPTJ0XGrLvf7pSOxfxKEHfmgRbxaV6KqLTb3mtMo1+8-vpncPA@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--cc=palves@redhat.com \
--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