Re: [Valgrind-developers] multiple passes over application

[Nicholas N. <nj...@ca...>]

On Tue, 6 Jan 2004, Ayodele Thomas wrote:

> Because of the memory requirements of my skin, I would like to do a
> preprocessing step where I look at all of the data addresses produced and
> dump a file containing addresses that are read only.  Then I
> want to read those addresses in and use them.  Currently, I
> have one skin that does the preprocessing and another than does
> the main processing.

Does the second step have to be done as a Valgrind skin -- could it be
done with a standalone program?  Or, can you do the pre-processing and the
main processing at the same time?  That seems a better way to do things.

> However, when I re-execute the code with the
> different skin, the memory addresses move and they no longer match up.

I think this is because the different skins have different sizes and thus
cause memory to be laid out in a different way.  When developing
Cachegrind, I found that the hit/miss counts would change slightly
whenever I made the slightest change to the skin code, for exactly this
reason.

> Is there a way to force the application to run a second time within the
> same skin? (i.e. make two passes).  I think then the addresses would be
> stable between the two runs.

Not that I'm aware of.

N