Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: Daniel Jacobowitz <drow@false.org>,
		Mark Kettenis <mark.kettenis@xs4all.nl>,
	gdb@sources.redhat.com
Subject: Re: Merge of nickrob-async-20060513 to mainline?
Date: Thu, 31 Aug 2006 23:33:00 -0000	[thread overview]
Message-ID: <17655.28994.979830.876998@kahikatea.snap.net.nz> (raw)
In-Reply-To: <1157064793.4466.52.camel@localhost.localdomain>

 > > It's their choice to make GDB multi-threaded.  I'm just saying it's an
 > > example of where it seems to work in practice.
 > 
 > Nick, what you're up against is that this is an old discussion.
 > We've tossed around the idea of making gdb a multi-threaded app
 > for years, and for various reasons, we've decided against it.

If it's an old discussion, it was presumably before NPTL, when LinuxThreads
was used.

 > Therefore there is some inertia involved here, and you're not 
 > gonna sell the idea casually.  

I'm not trying to sell the idea of threads (I wouldn't know how to) but
the idea of an asynchronous event loop (which might involve the use of
a single extra thread).

 > I suspect that some of us are reluctant to jump into the
 > discussion anew, with someone who doesn't have all of the 
 > history and context.

Sure, I think the focus of my original message has somehow shifted anyway.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-08-31 23:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  2:27 Nick Roberts
2006-08-30  2:33 ` Daniel Jacobowitz
2006-08-30  3:21   ` Nick Roberts
2006-08-30  4:01     ` Daniel Jacobowitz
2006-08-30 12:31       ` Eli Zaretskii
2006-08-30 21:34       ` Nick Roberts
2006-08-30 21:43         ` Daniel Jacobowitz
2006-08-30 23:45           ` Nick Roberts
2006-09-26  8:41           ` Nick Roberts
2006-09-26 12:38             ` Daniel Jacobowitz
2006-09-26 22:12               ` Nick Roberts
2006-09-26 22:24                 ` Daniel Jacobowitz
2006-09-26 23:40                   ` Nick Roberts
2006-09-29  1:50                   ` Nick Roberts
2006-10-06  0:53               ` Nick Roberts
2006-10-06  1:26                 ` Daniel Jacobowitz
2006-10-06  2:13                   ` Nick Roberts
2006-10-06  3:24                     ` Daniel Jacobowitz
2006-10-08  3:46                       ` Nick Roberts
2006-10-09 18:00                         ` async implies sync, was " Michael Snyder
2006-10-09 20:28                           ` async implies sync Nick Roberts
2006-08-31 21:03     ` Merge of nickrob-async-20060513 to mainline? Mark Kettenis
2006-08-31 21:49       ` Nick Roberts
2006-08-31 22:29         ` Daniel Jacobowitz
2006-08-31 22:40           ` Nick Roberts
2006-08-31 22:53             ` Michael Snyder
2006-08-31 23:33               ` Nick Roberts [this message]
2006-08-31 23:37                 ` Daniel Jacobowitz
2006-08-31 23:59                   ` Jim Ingham

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=17655.28994.979830.876998@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=Michael.Snyder@palmsource.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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