On Wednesday 04 March 2009, Dallman, John wrote: > > They indicate that valgrind's memory manager was asked to > > handle a block (actually a single contiguous address > > interval, which could be a block or a non-block) of more > > than 100,000,000 bytes ... on x86_64 with 64-bit addresses > > and much more latitude for placement of PT_LOAD, this
Harmless .. ignore it. Either one of your .so's has a data, text or bss section of size > 100MB, or (more likely) the app did a malloc/calloc/new etc of size > 100MB. If you really want to see, try --trace-malloc=yes. It doesn't indicate any defect in your code. It was probably of some use for the valgrind developers years ago. J ------------------------------------------------------------------------------ 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
