This is the mail archive of the
mailing list for the GDB project.
Re: non-blocking reads/writes and event loops
- To: Daniel Berlin <dan at cgsoftware dot com>
- Subject: Re: non-blocking reads/writes and event loops
- From: Jim Blandy <jimb at zwingli dot cygnus dot com>
- Date: 20 Jun 2000 12:20:50 -0500
- Cc: Andrew Cagney <ac131313 at cygnus dot com>, Todd Whitesel <toddpw at windriver dot com>, Jim Ingham <jingham at apple dot com>, gdb at sourceware dot cygnus dot com, "Insight (GDB GUI)" <insight at sourceware dot cygnus dot com>
- References: <Pine.LNX.firstname.lastname@example.org>
> 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.