Re: [Valgrind-users] Valgrind trace Memory Addresses while running?

[G N S. P. <gns...@ii...>]

Thanks for this information.

We are doing a memory system simulation, and need the address stream. At this point of time, we don't care if we need a Terabyte even, we can delete the files later.

Is there anything we can use from Valgrind?

Best
________________________________
From: John Reiser <jr...@bi...>
Sent: 06 August 2022 01:18
To: val...@li... <val...@li...>
Subject: Re: [Valgrind-users] Valgrind trace Memory Addresses while running?

>> if we can get a list of all the physical addresses the program used, in the order the program accessed them, and whether read/write.


>  For any real world application the size of the log would be overwhelmingly huge ... (unless you only want unique addresses).

Of course this is the purpose of data compression (such as gzip, etc).
You get some/much/most of the benefit of restricting to unique addresses
while still capturing the entire stream of references.

But as Paul noted, valgrind works in virtual addresses.
Getting all the actual physical addresses is close to impossible.
If you are working in an embedded device environment
and care only about a small handful of memory-mapped
device registers, then you can (must) process the
mapping yourself.





_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users