From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17504 invoked by alias); 14 Oct 2003 15:24:22 -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 17495 invoked from network); 14 Oct 2003 15:24:20 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 14 Oct 2003 15:24:20 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6DAA02B89; Tue, 14 Oct 2003 11:24:19 -0400 (EDT) Message-ID: <3F8C1523.5040704@redhat.com> Date: Tue, 14 Oct 2003 15:24:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz , Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0 References: <20031014054225.GB919@gnat.com> <20031014125731.GA14097@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00448.txt.bz2 > On Mon, Oct 13, 2003 at 10:42:25PM -0700, Joel Brobecker wrote: > >> We now basically get almost nothing: >> >> #0 0xffffe002 in ?? () >> #1 0x4002d379 in pthread_cond_wait@@GLIBC_2.3.2 () >> from /lib/tls/libpthread.so.0 Joel, what happens if you type: (gdb) x/i 0xffffe002 Andrew > That's NPTL. Are you sure you understand the problem right - I don't > have RH9's glibc here, only Rawhide's, but there's CFI for > pthread_cond_wait in Rawhide. > > So anyway this _will_ go away someday. > > >> The problem I am now trying to solve is the following: How can we fix >> the i386 unwinder to be smart enough to handle this wicked function? >> Is this even possible? The only possibility I see right now is with >> dwarf2 CFI, but then the problem I foresee is that we can not help >> the people using the stock RH9. If the only hope is with CFI, then >> they will have to update their pthread library... > > > You really can't unwind past this sort of thing without either debug > info or frame pointers. How did it work in 5.3? I'm assuming dumb > luck, we unwound 0xfffffe02 wrong. >