This is the mail archive of the
mailing list for the GDB project.
Re: gdb stack trace unreadable for a pthreads application
- From: Paul Pluzhnikov <ppluzhnikov at google dot com>
- To: x x <bapluda at yahoo dot com dot br>
- Cc: gdb at sourceware dot org
- Date: Thu, 30 Apr 2009 09:56:32 -0700
- Subject: Re: gdb stack trace unreadable for a pthreads application
- References: <firstname.lastname@example.org>
On Thu, Apr 30, 2009 at 9:19 AM, x x <email@example.com> 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.