From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11112 invoked by alias); 20 Jun 2008 13:54:54 -0000 Received: (qmail 11081 invoked by uid 22791); 20 Jun 2008 13:54:49 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Jun 2008 13:54:28 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m5KDsRa5005005 for ; Fri, 20 Jun 2008 09:54:27 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5KDsQQw021078 for ; Fri, 20 Jun 2008 09:54:26 -0400 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5KDsLmK011076 for ; Fri, 20 Jun 2008 09:54:21 -0400 Message-ID: <485BB695.5060101@redhat.com> Date: Sat, 21 Jun 2008 14:14:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: frysk Subject: back-traces back to normal Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00112.txt.bz2 FYI, I've been fixing a number of symbol related problems that can be seen when doing backtraces, for instance: On F-9: $ ./frysk/bindir/fstack $$ Task #18929 #0 0x000000310d49a835 in __waitpid() from libc-2.7.so #1 0x0000000000435a51 in [unknown] from bash #2 0x000000000043786e in wait_for() from bash ... frame #1 is now correctly reporting [unknown], an elfutils regression was causing _start to be printed. and on F-8: $ ./frysk/bindir/fstack $$ Task #11813 #0 0x00110416 in __kernel_vsyscall() from [vdso] #1 0x0807d210 in wait_for() from bash ... frame #1 has [vdso] and the symbol appearing again, a fix while converting cni to jni caused this I've added/enabled tests to check for both of these cases. Andrew