From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26032 invoked by alias); 2 May 2002 19:34:21 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26021 invoked from network); 2 May 2002 19:34:19 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 2 May 2002 19:34:19 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 173MLR-0005Vc-00; Thu, 02 May 2002 15:34:25 -0400 Date: Thu, 02 May 2002 12:34:00 -0000 From: Daniel Jacobowitz To: Kevin Buettner Cc: gdb@sources.redhat.com Subject: Re: RFC: Two small remote protocol extensions Message-ID: <20020502193425.GA20980@nevyn.them.org> Mail-Followup-To: Kevin Buettner , gdb@sources.redhat.com References: <20020502022543.GA22594@nevyn.them.org> <3CD15D5A.7020308@cygnus.com> <20020502155203.GA12647@nevyn.them.org> <3CD16BC9.2010209@cygnus.com> <20020502191411.GB19130@nevyn.them.org> <1020502192235.ZM30618@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1020502192235.ZM30618@localhost.localdomain> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-05/txt/msg00016.txt.bz2 On Thu, May 02, 2002 at 12:22:35PM -0700, Kevin Buettner wrote: > On May 2, 3:14pm, Daniel Jacobowitz wrote: > > > Heck, if I can work out a way to do it safely, I intend to do > > one-thread-stopped-only SVR4 shared library support also. > > Can you explain what you mean by this? I'd like to (where possible; probably not in every circumstance!) update the shared library information without stopping all threads. At least glibc's dynamic linker does enough locking on its own (so that multiple threads calling dlopen() do not trample each other) that when one thread has stopped it is safe to examine the link maps; I assume that this is true for other systems which support both threads and dlopen as well (e.g. Solaris). As I said in the original message, starting Apache 2 in multithreaded mode stops all threads every time a module is loaded; that's painful, since I believe modules can be loaded after server threads have been created (and on demand, per-request, in some cases). The mod_perl developers were complaining about the speed hit several months ago. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer