From: Tom Tromey <tom@tromey.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC 0/6] Demangle minimal symbol names in worker threads
Date: Mon, 11 Mar 2019 22:40:00 -0000 [thread overview]
Message-ID: <87a7i1826o.fsf@tromey.com> (raw)
In-Reply-To: <579bea0e-1efe-ae42-5d09-c5d53ba340a2@FreeBSD.org> (John Baldwin's message of "Mon, 11 Mar 2019 10:26:52 -0700")
>>>>> "John" == John Baldwin <jhb@FreeBSD.org> writes:
Tom> I have some more ideas for areas in gdb that could benefit from
Tom> threads. I'm happy to discuss if you're interested.
John> My only caution here is that I find it handy that I can use single
John> stepping to debug many of the things I encounter in gdb, especially
John> the main event loop.
At least for the "parallel for" code that is in this series, it would be
simple to add a debugging flag to force it to take the single-thread
path.
Tom
prev parent reply other threads:[~2019-03-11 22:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 17:23 Tom Tromey
2019-03-09 17:23 ` [RFC 6/6] Demangle minsyms in parallel Tom Tromey
2019-03-09 17:23 ` [RFC 3/6] Lock the demangled hash table Tom Tromey
2019-03-09 17:23 ` [RFC 1/6] Defer minimal symbol name-setting Tom Tromey
2019-03-09 17:23 ` [RFC 4/6] Introduce run_on_main_thread Tom Tromey
2019-03-09 17:23 ` [RFC 2/6] Remove static buffer from ada_decode Tom Tromey
2019-03-09 17:23 ` [RFC 5/6] Introduce thread-safe way to handle SIGSEGV Tom Tromey
2019-03-11 17:24 ` John Baldwin
2019-03-09 18:09 ` [RFC 0/6] Demangle minimal symbol names in worker threads Eli Zaretskii
2019-03-11 17:35 ` John Baldwin
2019-03-11 22:39 ` Tom Tromey
2019-03-12 3:33 ` Eli Zaretskii
2019-03-13 15:38 ` Eli Zaretskii
2019-03-15 23:28 ` Tom Tromey
2019-03-16 7:46 ` Eli Zaretskii
2019-03-16 8:31 ` Eli Zaretskii
2019-03-15 23:40 ` Tom Tromey
2019-03-16 7:52 ` Eli Zaretskii
2019-03-11 17:26 ` John Baldwin
2019-03-11 22:40 ` Tom Tromey [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=87a7i1826o.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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