gdb stack trace unreadable for a pthreads application

[Paul Pluzhnikov]

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