From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: x x <bapluda@yahoo.com.br>
Cc: gdb@sourceware.org
Subject: Re: gdb stack trace unreadable for a pthreads application
Date: Thu, 30 Apr 2009 19:03:00 -0000 [thread overview]
Message-ID: <8ac60eac0904300956q6e22e3ces3b1826ccaeca9ca@mail.gmail.com> (raw)
In-Reply-To: <481435.21529.qm@web38104.mail.mud.yahoo.com>
On Thu, Apr 30, 2009 at 9:19 AM, x x <bapluda@yahoo.com.br> 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
next prev parent reply other threads:[~2009-04-30 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 16:30 x x
2009-04-30 19:03 ` Paul Pluzhnikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-25 14:43 x x
2009-04-27 0:43 ` Paul Pluzhnikov
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=8ac60eac0904300956q6e22e3ces3b1826ccaeca9ca@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=bapluda@yahoo.com.br \
--cc=gdb@sourceware.org \
/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