From: John Baldwin <jhb@FreeBSD.org>
To: 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 17:26:00 -0000 [thread overview]
Message-ID: <579bea0e-1efe-ae42-5d09-c5d53ba340a2@FreeBSD.org> (raw)
In-Reply-To: <20190309172300.2764-1-tom@tromey.com>
On 3/9/19 9:22 AM, Tom Tromey wrote:
> I have some more ideas for areas in gdb that could benefit from
> threads. I'm happy to discuss if you're interested.
My only caution here is that I find it handy that I can use single
stepping to debug many of the things I encounter in gdb, especially
the main event loop. When I've worked with lldb I've found single
stepping less useful and have had to rely on their builtin tracing
framework to usefully debug things. Peeling off tasks that aren't
part of the main event loop probably won't impact that, but I think
it's worth considering that tradeoff for future patches at least.
--
John Baldwin
next prev parent reply other threads:[~2019-03-11 17:26 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 3/6] Lock the demangled hash table Tom Tromey
2019-03-09 17:23 ` [RFC 6/6] Demangle minsyms in parallel 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 17:23 ` [RFC 4/6] Introduce run_on_main_thread Tom Tromey
2019-03-09 17:23 ` [RFC 1/6] Defer minimal symbol name-setting Tom Tromey
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 [this message]
2019-03-11 22:40 ` 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=579bea0e-1efe-ae42-5d09-c5d53ba340a2@FreeBSD.org \
--to=jhb@freebsd.org \
--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