Valgrind says “stack allocation,” I say “heap allocation”?

I don't know what the problem is, but -track-origins=yes might help get you more information about what it's complaining about; see this blog post for details: blog.mozilla.com/nnethercote/2009/02/27/....

I'm using track-origins; I forgot to mention that. Could it be leading me astray? – Joel J.

Adamson Apr 21 '10 at 17:17.

Possible reason: you define age_dep_data->mtable as double* but it should be double** to be an array of arrays.

I allocate an array of size n*(size of a pointer to double), then for each pointer in that array I allocate an array of size m*(size of a double). Do I need to use sizeof(double **) in the call to malloc()? – Joel J.

Adamson Apr 21 '10 at 17:15 1 no, you code is okey; we can't see the declaration of age_dep_data->mtable - it should be declared as double** – oraz Apr 21 '10 at 17:35 It is declared as double ** within a structure (also dynamically allocated). – Joel J. Adamson Apr 21 '10 at 18:55 ok, then I pass – oraz Apr 21 '10 at 20:53.

I have since found that this valgrind error Conditional jump or move depends on uninitialised value(s) happens all the time and is not the source of the error. It appears to be a red herring in most cases I've encountered since posting this question.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.