From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31713 invoked by alias); 23 Oct 2003 02:41:43 -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 31704 invoked from network); 23 Oct 2003 02:41:42 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 23 Oct 2003 02:41:42 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1ACVPv-0000ia-Kb; Wed, 22 Oct 2003 22:41:39 -0400 Date: Thu, 23 Oct 2003 02:41:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0 Message-ID: <20031023024139.GC2637@nevyn.them.org> Mail-Followup-To: Joel Brobecker , gdb-patches@sources.redhat.com References: <20031014054225.GB919@gnat.com> <20031023010754.GQ701@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031023010754.GQ701@gnat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00679.txt.bz2 On Wed, Oct 22, 2003 at 06:07:54PM -0700, Joel Brobecker wrote: > Hello, > > the discussion regarding this problem showed that we can not basically > do much in that case... > > Still, I was wondering if you were interested in a new gdb.threads test. > As far as I can see, none of our current thread test seems to be > catching the problem I reported. > > Basically, the C code would create a new thread, that we would block > on a call to pthread_cond_wait(). After reaching a breakpoint in the > main procedure, we would swith to the blocked thread, and try to get > a backtrace. > > I can also open a PR... > > Let me know. New testcases are always appreciated. It may end up being XFAIL'd for some cases, though. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer