From: Jeffrey Walton <noloader@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: GDB Users List <gdb@sourceware.org>
Subject: Re: Interpret object causing crash in __cxa_finalize (have core)
Date: Wed, 24 Aug 2011 19:54:00 -0000 [thread overview]
Message-ID: <CAH8yC8kRcBemPfkHBrjXvOgQfg-+tVBkd9zbYL_yCFWERt4v0A@mail.gmail.com> (raw)
In-Reply-To: <20110824193938.GA18325@host1.jankratochvil.net>
On Wed, Aug 24, 2011 at 3:39 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Wed, 24 Aug 2011 21:31:14 +0200, Jeffrey Walton wrote:
>> I'm observing an intermittent crash during unloading of a shared
>> object. The library and test harness were built with '-g3 -ggdb -O0',
>> and 'ulimit -c unlimited', so I am able to get it under GDB.
>
> If you have it reproducible run it under valgrind first.
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=CAH8yC8k0QAqj%2B4eyQ%3D20aH11Tnb7m43%3DxjCdkxKZY8ssgf3rfg%40mail.gmail.com&forum_name=valgrind-users.
>> But I'm having problems interpreting what object is being problematic.
> [...]
>> #21 0x00002ba649808630 in __cxa_finalize (d=0x2ba64901c3d8)
>> at cxa_finalize.c:56
>> check = <value optimized out>
>> cxafn = 0x6
>> cxaarg = 0xa46
>> f = 0x13925e0
>> funcs = 0x13924f0
>> (gdb) po 0x13925e0
>> evaluation of this expression requires the target program to be active
>
> print-object is for Objecttive-C. And you will decode there just the info you
> see in the frame #20.
Indeed! I've been working on iPhones/iPads for too long.
> This looks as a memory corruption, it is better to debug instrument the code
> leading to this state, this core file may no longer be too useful.
Ok, thanks.
To retain info on the objects in question, do I need to compile with
g++ -v and save the intermediate (ii?) files?
Jeff
> [...]
>> #20 0x0000000000470c0a in ~map (this=0x83dfc0, __in_chrg=<value optimized out>)
>> at /usr/include/c++/4.4/bits/stl_map.h:87
>> No locals.
>> #21 0x00002ba649808630 in __cxa_finalize (d=0x2ba64901c3d8)
>> at cxa_finalize.c:56
>> check = <value optimized out>
>> cxafn = 0x6
>> cxaarg = 0xa46
>> f = 0x13925e0
>> funcs = 0x13924f0
>> #22 0x00002ba648c59076 in __do_global_dtors_aux () from lib/libesapi-c++.so
>> No symbol table info available.
>> #23 0x0000000000000000 in ?? ()
>> No symbol table info available.
>> (gdb)
>
next prev parent reply other threads:[~2011-08-24 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 19:31 Jeffrey Walton
2011-08-24 19:40 ` Jan Kratochvil
2011-08-24 19:54 ` Jeffrey Walton [this message]
2011-08-24 20:03 ` Jan Kratochvil
2011-08-24 20:19 ` Jeffrey Walton
2011-08-24 20:34 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH8yC8kRcBemPfkHBrjXvOgQfg-+tVBkd9zbYL_yCFWERt4v0A@mail.gmail.com \
--to=noloader@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox