* [ECOS] about memory on ecos
@ 2007-07-26 6:41 dengdd
2007-07-26 6:57 ` Andrew Lunn
0 siblings, 1 reply; 2+ messages in thread
From: dengdd @ 2007-07-26 6:41 UTC (permalink / raw)
To: ecos-discuss
hi ,list
I am just starting to learn to develop with eCos.
i am working on hp ipaq 3630.
Now, my application can run .
I want to know how much memorys free on eCos when my application
running. But i don't know how to do it.
or know how much memorys my application used ?
Any ideas?
thanks ,Good luck .
Dongdong
mailto: dengdd@minigui.org
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ECOS] about memory on ecos
2007-07-26 6:41 [ECOS] about memory on ecos dengdd
@ 2007-07-26 6:57 ` Andrew Lunn
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Lunn @ 2007-07-26 6:57 UTC (permalink / raw)
To: dengdd; +Cc: ecos-discuss
On Thu, Jul 26, 2007 at 02:40:49PM +0800, dengdd wrote:
> hi ,list
> I am just starting to learn to develop with eCos.
> i am working on hp ipaq 3630.
> Now, my application can run .
>
> I want to know how much memorys free on eCos when my application
> running. But i don't know how to do it.
> or know how much memorys my application used ?
mallinfo will tell you about the heap. If you are using eCos variable
of fixed size memory blocks, you can call cyg_mempool_var_get_info()
or cyg_mempool_fix_get_info().
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-07-26 6:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-26 6:41 [ECOS] about memory on ecos dengdd
2007-07-26 6:57 ` Andrew Lunn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).