From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19342 invoked by alias); 9 Jan 2003 00:48:50 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19320 invoked from network); 9 Jan 2003 00:48:49 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by 209.249.29.67 with SMTP; 9 Jan 2003 00:48:49 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h090KqB02675 for ; Wed, 8 Jan 2003 19:20:52 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h090man28772; Wed, 8 Jan 2003 19:48:36 -0500 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id h090mZE07202; Wed, 8 Jan 2003 16:48:35 -0800 Message-ID: <3E1CC6E3.51B1227F@redhat.com> Date: Thu, 09 Jan 2003 00:48:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb-patches@sources.redhat.com Subject: Re: threads and target-function-calls References: <3E1B7829.6B6E8BAF@redhat.com> <20030108010842.GA30628@nevyn.them.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00354.txt.bz2 Daniel Jacobowitz wrote: > > On Tue, Jan 07, 2003 at 05:00:25PM -0800, Michael Snyder wrote: > > Hey folks, > > > > Did you know that (at least on x86 linux), if you have a multi-thread > > program and you execute a target function call, all the threads get to > > run? Doesn't that seem like a bad thing? Wouldn't we really rather > > only run the thread that is executing the target function call? > > Eeeeek! I think I agree with you here; that's the logical behavior. > It never occured to me to try. I just happened to have "debug lin-lwp" turned on. Perhaps we need to think about what "target function call" actually means in the presence of threads that can interact with each other.