Re: Function stack reallocation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Reggie Cushing wrote:
> Hi All - I wish some insight on the possibility of reallocating a
> function stack to a malloced regions in realtime ie I jump out of a
> function and the next time I jump in the stack would have moved along
> with its data. To me it seems unreliable cause the values in the stack
> have no type hence I would not know if the stack value is a data value
> or a pointer. If I mistakenly interpret a data value as a pointer I will
> update the data value resulting in data corruption. I would really wish
> some expert insight in this on this subject.

What you're talking about is something long these lines:

a=malloc(chunk);
memcpy( chunk, SP, size);
SP=chunk;


The only way you "know" what's on your stack is by the variable
declarations you've made in your code.  The stack, wherever it is, does
not contain any type info.


/Per Jessen, Zurich
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Assembler]     [Git]     [Kernel List]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [C Programming]     [Yosemite Campsites]     [Yosemite News]     [GCC Help]

  Powered by Linux