- Original Message -
Dear Valgrind community,
I am currently trying to use massif on a huge programming project,
and I
want to isolate some allocations that aren't significant.
I use the --ignore-fn option like this:
valgrind --tool=massif --ignore-fn=SDL_CreateRGBSurface
Hello,
I will try it. How do you find mangled names in a huge project?
There is still the question why some of the C++ --ignore-fn are
respected even without mangling.
Best regards
Marian Kechlibar
--
Live Security
On Tue, Apr 24, 2012 at 11:45 AM, Julian Seward jsew...@acm.org wrote:
Maybe the s or some other characters in the command line arguments
are not getting handled properly by the shell?
in bash:
$ echo ab
ab
$ echo 'ab'
ab
$ echo ab
[1] 4711 - Process ID of background
Hello,
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).
Is it possible to suppress all allocations from certain library,
Not sure how to post to this thread having just signed up for the
list, but hopefully this routes correctly..
Hi,
I wanted to confirm that the aes changes in trunk do indeed solve that
unrecognized instruction issue, however,
I am still experiencing immediate termination whenever I use valgrind
On Tue, 2012-04-24 at 14:06 -0400, Matt Broadstone wrote:
Not sure how to post to this thread having just signed up for the
list, but hopefully this routes correctly..
Hi,
I wanted to confirm that the aes changes in trunk do indeed solve that
unrecognized instruction issue, however,
I am
