From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5594 invoked by alias); 30 Apr 2009 16:56:45 -0000 Received: (qmail 5577 invoked by uid 22791); 30 Apr 2009 16:56:43 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Apr 2009 16:56:36 +0000 Received: from zps78.corp.google.com (zps78.corp.google.com [172.25.146.78]) by smtp-out.google.com with ESMTP id n3UGuYMq011482 for ; Thu, 30 Apr 2009 09:56:34 -0700 Received: from qw-out-1920.google.com (qwk4.prod.google.com [10.241.195.132]) by zps78.corp.google.com with ESMTP id n3UGuDWK025524 for ; Thu, 30 Apr 2009 09:56:33 -0700 Received: by qw-out-1920.google.com with SMTP id 4so1392793qwk.20 for ; Thu, 30 Apr 2009 09:56:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.82.15 with SMTP id z15mr1487911qck.32.1241110592662; Thu, 30 Apr 2009 09:56:32 -0700 (PDT) In-Reply-To: <481435.21529.qm@web38104.mail.mud.yahoo.com> References: <481435.21529.qm@web38104.mail.mud.yahoo.com> Date: Thu, 30 Apr 2009 19:03:00 -0000 Message-ID: <8ac60eac0904300956q6e22e3ces3b1826ccaeca9ca@mail.gmail.com> Subject: Re: gdb stack trace unreadable for a pthreads application From: Paul Pluzhnikov To: x x Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00235.txt.bz2 On Thu, Apr 30, 2009 at 9:19 AM, x x wrote: > I am building and running mfsrv exactly from the same machine and same > directory. And I am analyzing the core also from the same machine and same > user account. I am running on a chrooted system. Could this be the cause of > the path mismatch? Perhaps. Are you in the same chroot when SIGSEGV happens, and when you analyze the core with GDB? You should be. > How can I view which libraries it is using when running, > and make sure that gdb uses the same? You could "md5sum /lib/tls/i686/cmov/libc.so.6" just before running the application and "shell md5sum /lib/tls/i686/cmov/libc.so.6" at the (gdb) prompt. They should exactly match. Cheers, -- Paul Pluzhnikov