From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6442 invoked by alias); 24 Aug 2011 20:19:01 -0000 Received: (qmail 6424 invoked by uid 22791); 24 Aug 2011 20:19:00 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_CX X-Spam-Check-By: sourceware.org Received: from mail-wy0-f169.google.com (HELO mail-wy0-f169.google.com) (74.125.82.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 24 Aug 2011 20:18:46 +0000 Received: by wyi11 with SMTP id 11so1346355wyi.0 for ; Wed, 24 Aug 2011 13:18:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.71.5 with SMTP id q5mr1025336wed.4.1314217125352; Wed, 24 Aug 2011 13:18:45 -0700 (PDT) Received: by 10.216.62.72 with HTTP; Wed, 24 Aug 2011 13:18:45 -0700 (PDT) Reply-To: noloader@gmail.com In-Reply-To: <20110824200308.GA20742@host1.jankratochvil.net> References: <20110824193938.GA18325@host1.jankratochvil.net> <20110824200308.GA20742@host1.jankratochvil.net> Date: Wed, 24 Aug 2011 20:19:00 -0000 Message-ID: Subject: Re: Interpret object causing crash in __cxa_finalize (have core) From: Jeffrey Walton To: Jan Kratochvil Cc: GDB Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: 2011-08/txt/msg00108.txt.bz2 On Wed, Aug 24, 2011 at 4:03 PM, Jan Kratochvil wrote: > On Wed, 24 Aug 2011 21:54:09 +0200, Jeffrey Walton wrote: >> Boost has made Valgrind useless (15000 line of output). And I have not >> been successful in getting suppression rules: >> http://lists.boost.org/boost-users/2011/08/70235.php and >> http://sourceforge.net/mailarchive/forum.php?thread_name=3DCAH8yC8k0QAqj= %2B4eyQ%3D20aH11Tnb7m43%3DxjCdkxKZY8ssgf3rfg%40mail.gmail.com&forum_name=3D= valgrind-users. > > You do not need to track memory leaks but you should track memory corrupt= ions. > You was told the same in the mails. We are also interested in memory leaks - other libraries affect our integri= ty. OT: we're finding these other libraries are somewhat sloppy, and are affecting our ability to analyze our stuff. They need to fix their gear, or we need to find suppression rules. >> To retain info on the objects in question, do I need to compile with >> g++ -v and save the intermediate (ii?) files? > > I do not see any missing debug info in your backtrace. > > g++ uses -g for debug info, not -v. Yes, we have -g3 -ggdb. But we seem to be missing diagnostic information from __do_global_dtors_aux and __cxa_finalize. > You did not tell which platform do you run on but it seems to me like > GNU/Linux, debug info is stored there in the binary files or in separate > .debug info files (one file per one library) in /usr/lib/debug. =A0The de= bug > info stored in object files is specific only to Apple OSes. My bad. This is a C++ library (non-Apple). $ uname -a Linux studio 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:07:13 UTC 2011 x86_64 GNU/Linux > But after all you have all the debug info you can have in that backtrace. OK, I' seem to have a misconception. Is there no debug information associated with global constructors and destructors? If not, how does one determine the problematic object destructor? Lumping everything into __cxa_finalize is not helpful. Jeff