From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2430 invoked by alias); 31 May 2007 18:35:59 -0000 Received: (qmail 2416 invoked by uid 22791); 31 May 2007 18:35:59 -0000 X-Spam-Check-By: sourceware.org Received: from nz-out-0506.google.com (HELO nz-out-0506.google.com) (64.233.162.234) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 31 May 2007 18:35:55 +0000 Received: by nz-out-0506.google.com with SMTP id s1so219316nze for ; Thu, 31 May 2007 11:35:53 -0700 (PDT) Received: by 10.114.148.1 with SMTP id v1mr942820wad.1180636553529; Thu, 31 May 2007 11:35:53 -0700 (PDT) Received: by 10.114.190.20 with HTTP; Thu, 31 May 2007 11:35:53 -0700 (PDT) Message-ID: Date: Thu, 31 May 2007 18:35:00 -0000 From: "Ulisses Furquim" To: gdb@sourceware.org Subject: Re: Problems with multi-threaded application debugging Cc: "Ulisses Furquim" In-Reply-To: <20070531170448.GB23197@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070531170448.GB23197@localhost.localdomain> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-05/txt/msg00185.txt.bz2 Hi Daniel, On 5/31/07, Daniel Jacobowitz wrote: > > - sometimes when you "continue" gdb doesn't stop at a breakpoint > > inside some of the threads; > > - sometimes when you try to single step (with "next") all the threads > > run until the program exits; > > I have no idea what these might be. Yeah, I thought it was really strange and I can trigger this behavior with a really simple application. > > - I was trying to use the scheduler-locking variable (setting it to > > "on"), but it seems I can single step on only one thread. I mean, If I > > switch to another thread and try to single step it, gdb switches back > > to the previous thread. > > To be honest, I can't completely remember whether this is supposed to > happen still or supposed to be fixed. You need to be using a current > version of gdb and gdbserver, but GDB may still be doing something > wrong. Ah, I'm sorry, I wasn't completely clear. I forgot to say that I can trigger all those problems with gdb 6.4-debian (from Ubuntu Edgy) on a x86 machine and also with gdb 6.6 on an ARM device. I'm not even using gdbserver (yet). Regards, -- Ulisses