H
Horacius ReX
Hi,
I am developing some code which first I compile with VS and afterwards
I test on another special hardware which has almost no debug
capabilities at all. Usually I get a lot of errors in the latter,
because I have memory size limitations. So, I wonder what are the best
practices in VS to know for a given program, once it is compiled and
before its execution:
- what will be the stack size available for the program
- what will be the size of the code
- what will be the size of the allocated data (global variables, etc)
- if it is also possible to estimate the size of the heap used
Thanks in advance
H
I am developing some code which first I compile with VS and afterwards
I test on another special hardware which has almost no debug
capabilities at all. Usually I get a lot of errors in the latter,
because I have memory size limitations. So, I wonder what are the best
practices in VS to know for a given program, once it is compiled and
before its execution:
- what will be the stack size available for the program
- what will be the size of the code
- what will be the size of the allocated data (global variables, etc)
- if it is also possible to estimate the size of the heap used
Thanks in advance
H