>> Where are your PT_LOAD? [/usr/include/elf.h; shown as just "LOAD" by >> readelf]
> Output of readelf --segments for the executable is: > Program Headers: [high 32 bits of 0 have been elided] > Type Offset VirtAddr PhysAddr > FileSiz MemSiz Flags Align > LOAD 0x00000000 0x00400000 0x00400000 > 0x0031c544 0x0031c544 R E 100000 > LOAD 0x0031d000 0x0081d000 0x0081d000 > 0x00012fe8 0x0005ac20 RW 100000 > and the same for the shared library that is probably the cause - > LOAD 0x00000000 0x00000000 0x00000000 > 0x003d0d2d 0x003d0d2d R E 100000 > LOAD 0x003d1000 0x004d1000 0x004d1000 > 0x00004d2c 0x00005b30 RW 100000 Those are as usual, with only the alignment gap of 0x100000 (1MB) between PT_LOAD of any one module. There is nothing to worry about there. As Julian says, run with --trace-malloc=yes to investigate further. And the valgrind developers should change the message to include the actual address, or remove the message entirely. -- ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
