Re: [Valgrind-developers] multiple passes over application

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

On Wed, 7 Jan 2004, Ayodele Thomas wrote:

> My initial step is designed to identify data addresses that are read only
> so that they can be excluded from the main analysis performed by the
> second step. Therefore, the second step is the critical step and must be
> performed in Valgrind.    I can't think of a way that both steps can be
> performed at the same time because the goal is to determine which data can
> be ignored - but that cannot be determined until the entire application
> has run because I am locating dependencies.

So you can't tell which addresses are read only until the program has
finished?  Ok, I think I understand.

> The initial step is designed to reduce the memory requirements because I must
> keep track of a tremendous amount of state in the main pass and have
> issues running out of memory and crashing, even with the 2GB of memory on
> my machine.

What about if you put both passes into the same skin, and then switch
between the pre-processing and main processing with a command-line arg?
That way, you will hopefully get the same memory addresses for both runs.
However, even if it does work, it sounds fragile.

N