From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Todd Whitesel <toddpw@windriver.com>,
Jim Ingham <jingham@apple.com>,
gdb@sourceware.cygnus.com,
"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: non-blocking reads/writes and event loops
Date: Tue, 20 Jun 2000 10:20:00 -0000 [thread overview]
Message-ID: <np1z1sfevh.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10006182227270.24967-100000@propylaea.anduin.com>
> The question about whether we *should* use threads is a different
> one altogether. The real question splits into "Are there parts of
> gdb where we could be doing processing that isn't dependent on other
> processing, and we therefore are possibly wasting time on MP systems
> by not having each done in a thread" and "Are there parts of GDB
> where we could simplify code flow by using threads".
Srikanth at HP has mentioned the idea of doing symbol table reads in
the background. I thought that sounded pretty cool.
next prev parent reply other threads:[~2000-06-20 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 3:13 Andrew Cagney
2000-06-12 18:47 ` Todd Whitesel
2000-06-14 10:07 ` Jim Ingham
2000-06-14 10:47 ` Todd Whitesel
2000-06-14 18:37 ` Andrew Cagney
2000-06-14 18:49 ` Todd Whitesel
2000-06-18 22:21 ` Andrew Cagney
2000-06-18 22:46 ` Daniel Berlin
2000-06-20 10:20 ` Jim Blandy [this message]
2000-06-20 3:43 ` Todd Whitesel
2000-06-20 7:35 ` Elena Zannoni
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=np1z1sfevh.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=ac131313@cygnus.com \
--cc=dan@cgsoftware.com \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@apple.com \
--cc=toddpw@windriver.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).