On Thursday 19 February 2009, Chengnian Sun wrote:
I have a question. How much information I could get from the debug-info?
That depends on the debug info format used; I think you can concentrate
on DWARF. You can check out in the specifiation what is available in
principle, then look what a
AFAIK, Julian recently added some functions to get at variable name for
a given stack address. You need it the other way around: get information
about number of parameter and types, and how to access them.
Yes, that information (parameter names and types) is definitely in the
Dwarf3, and the
Has anybody had any success with Valgrind 3.4 on PPC32?I'd appreciate your
input.
Thanks.
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source:
On Thu, Feb 19, 2009 at 4:54 PM, linux user linuxuse...@gmail.com wrote:
Has anybody had any success with Valgrind 3.4 on PPC32?I'd appreciate your
input.
According to the e-mails posted on the valgrind-users mailing list
during the last few weeks, several people are running Valgrind 3.4
On Thu, Feb 19, 2009 at 7:03 PM, linux user linuxuse...@gmail.com wrote:
From what I understand,Valgrind 3.2.3 supports Helgrind.
No, it does not.
Try 3.4.1
--kcc
It would be great if
you could let me know if you are able to run Helgrind from the Valgrind
3.2.3 suite.After having built
Konstatntin,
So Valgrind 3.2.3 doesn't support Helgrind.Why doesn't the
documentation/user manual for 3.2.3 say that?
This is what the doc states:
Note: Helgrind does not work in Valgrind 3.1.0. We hope to reinstate in
version 3.2.0.
That statement made me think that Valgrind 3.2.3 supports
Hi,
I am a new user to Valgrind tool.
I am trying to do cache profiling for a multi-threaded program written in C. I
am using cachegrind to do so. Though the output is really descriptive, I could
not find the results of L1 and L2 cache misses for different cores. I am
running the
