Horacius ReX
9/22/2008 3:05:00 PM
Sorry, I forgot to mention, the language is C
On Sep 22, 2:34 pm, "PvdG42" <p...@toadstool.edu> wrote:
> "Horacius ReX" <horacius....@gmail.com> wrote in message
>
> news:ff8c3224-52ad-4f14-9e36-be46d6c731ca@i76g2000hsf.googlegroups.com...
>
>
>
> > 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
>
> Before anybody can answer, how about some details? What language are you
> using? Memory allocation for a given data type is part of a given language
> (or technology platform) specification. This sounds like a non-.NET
> application, perhaps C++? Give us the above and the target platform
> information for meaningful answers.