On Tue, Apr 24, 2012 at 7:22 PM, Marian Kechlibar <[email protected]> wrote: > I found out... > > CRYPTO_malloc does not allocate the memory itself. It invokes some other > function within libssl.so. > This function does not have any name, and is shown as ??? > > (I use massif visualizer to view the results).
The function surely has a name, but valgrind is not able to find out the name, because you are probably not linking to the debug version (-g -O0) of the library. If you can, it is always nice to link to the debug versions of your dependencies, alas slower. ~manuel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
