This forum may not be the best to ask the question, but the answers on the other forums (that i know) were generally with respect to C for desktop pc (where memory management is different from that in embedded) and this forum has knowledgeable embedded people. hence...
I was worried about the following situation:
void function1() { ... //other variables char* ptr = myary; ... ptr = ReadNandFlash("myfile"); ... } char* ReadNandFlash(char* Filename) { FILE* file; char temp_ary[256]; file = fopen(Filename, "r"); if(file == NULL) { return NULL; } while(!feof(file)) { fread(temp_ary, sizeof(char), 256, file); } fclose(file); return ary; }
will the 'temp_ary' be destroyed as only the pointer value is returned back to the function1()?
other way is to pass the 'myary' to 'ReadNandFlash()' This will work.
What you are trying to do may/may-not destroy the array data in the memory. But there is no guarantee of it working always. There may be other piece of code which may change the data (other piece of code can be threads, or may be even an badly written ISR)
...may be even an badly written ISR)
May even be well written ISR!
Yes - for processors that has a common stack for ISR and main code (this includes a lot of processor architectures), the ISR is guaranteed to overwrite auto variables from returned functions.
And this thread is "Non-Specific (Generic)" so we can't assume any ARM chips that switches stack.