From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17306 invoked by alias); 23 Oct 2003 01:07:57 -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 17299 invoked from network); 23 Oct 2003 01:07:56 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 23 Oct 2003 01:07:56 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id CB4EDD2D29; Wed, 22 Oct 2003 18:07:54 -0700 (PDT) Date: Thu, 23 Oct 2003 01:07:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0 Message-ID: <20031023010754.GQ701@gnat.com> References: <20031014054225.GB919@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031014054225.GB919@gnat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-10/txt/msg00671.txt.bz2 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. -- Joel