From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13602 invoked by alias); 14 Oct 2003 16:19:32 -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 13595 invoked from network); 14 Oct 2003 16:19:29 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (206.116.66.93) by sources.redhat.com with SMTP; 14 Oct 2003 16:19:29 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 532C1D2D29; Tue, 14 Oct 2003 09:19:25 -0700 (PDT) Date: Tue, 14 Oct 2003 16:19:00 -0000 From: Joel Brobecker To: Andrew Cagney Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0 Message-ID: <20031014161925.GD989@gnat.com> References: <20031014054225.GB919@gnat.com> <20031014125731.GA14097@nevyn.them.org> <3F8C1523.5040704@redhat.com> <20031014154649.GA989@gnat.com> <20031014155211.GB10669@nevyn.them.org> <3F8C2139.3040904@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F8C2139.3040904@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-10/txt/msg00463.txt.bz2 > No matter how much you patch GDB, GDB isn't going to dig itself out of > thishole. It's not able to access the code/data/whatever at that > address so it's never going to correctly unwind from it. It's actually able to do a decent job. The problem at hand is not due to the "kernel bug", but rather the lack of unwind information for the pthread_cond_wait() function. And I am afraid that pthread_cond_wait() is just one example. With GCC getting better and better at optimizing, we will likely see this more and more often... -- Joel