I always dread using 32 bit tools on 64 bit systems because
of all the rough edges likely to be lurking. This might be one
of them.
On Ubuntu 8.10 64 bit, given the trivial program
#include <sys/types.h>
#include <pwd.h>
#include <stdio.h>
int main(int argc, char **argv)
{
struct passwd *p = getpwnam("root");
printf("p is %p\n", p);
}
a 64 bit run produces output with good line numbers for glibc, e.g.
gcc x.c; valgrind --leak-check=full ./a.out
...
==30678== by 0x4F2462C: nss_parse_service_list (nsswitch.c:547)
whereas a 32 bit run produces output without line numbers for glibc, e.g.
gcc -m32 x.c; valgrind --leak-check=full ./a.out
...
==30698== by 0x490E4F0: nss_parse_service_list (in /lib32/libc-2.8.90.so)
I believe I've loaded debug symbols correctly, with
$ sudo apt-get install libc6-dbg
$ dpkg-query -L libc6-dbg | grep libc-2
/usr/lib/debug/lib/libc-2.8.90.so
/usr/lib/debug/lib32/libc-2.8.90.so
/usr/lib/debug/libc-2.8.90.so
Which memo did I miss?
I could probably work around this by just running a 32 bit operating
sytem, but the world is turning, and everyone around me is using
the 64 bit version; I need to support them, too.
Thanks,
Dan
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
