Thread: Array changes value after external function that does not call the array

My code looks like this at the moment;

Code:

	for (j=0; j<bfun_lines; j++)
	{
		printf("Attention! BEFORE main split array %i is %lf\n", j, split_array[j]);
	}

	
	encrypt_array = padme(encrypt_array, &n_value);

	for (j=0; j<bfun_lines; j++)
	{
		printf("Attention! AFTER main split array %i is %lf\n", j, split_array[j]);
	}

In the first printf I have the array I originally assigned to split_array and after the function call which doesn't call split_array, it prints a different array.

I am pretty stuck as to what to look for as I have no idea how this could happen? Any ideas or would you need to see more code?

I have no idea what you think you mean by "call split_array". Is split_array global? If so, it can be changed by any function that feels like it. Are either of these arrays "fake" arrays (i.e., pointers to double instead of double[])? If so, they might be pointing to the same place. Does your function do something crazy, like write past an array? If so, it will probably end up writing on some other piece of memory, which may very well be split_array.

It isn't global. Both arrays are pointers to double but they have been individually malloc'd (if that makes a difference).

By 'call split_array' I meant that I am not passing it through an external function.

The function reallocs memory to the array passing through it (which is not split_array) with

Code:

pad_array = realloc(array, (new_size)*sizeof(double));

with pad_array a pointer to a double in the external function.

Is there any way to avoid the memory being overwritten?

Are you saying split_array is being changed when you call padme() even though there are no references to it made? Then we'd need to see the code in padme() to spot any array/pointer out-of-bounds stuff.