From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12223 invoked by alias); 17 Jul 2003 19:20:01 -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 12198 invoked from network); 17 Jul 2003 19:20:00 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 17 Jul 2003 19:20:00 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id BAF3AB93B; Thu, 17 Jul 2003 12:19:59 -0700 (PDT) To: gdb Subject: Re: TARGET_SIGNAL_TRAP References: <20030717183214.GA25316@nevyn.them.org> From: David Carlton Date: Thu, 17 Jul 2003 19:20:00 -0000 In-Reply-To: <20030717183214.GA25316@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 17 Jul 2003 14:32:14 -0400") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-07/txt/msg00216.txt.bz2 On Thu, 17 Jul 2003 14:32:14 -0400, Daniel Jacobowitz said: > Every time that a breakpoint is hit, including one breakpoint set at > every shared library load/unload, thread creation, or sometimes thread > exit, all threads are stopped and restarted. That's the usual cause. > Signals also stop the process. If GDB isn't going to report the signal > then it doesn't stop all threads, but that does interfere with timing. Ah, thanks for the info. I wonder if it's the shared library loads that we're seeing. Hmm: we might even be able to control that one. David Carlton carlton@kealia.com