diff options
| author | Joel Sherrill <joel.sherrill@OARcorp.com> | 1999-07-09 19:36:51 +0000 |
|---|---|---|
| committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 1999-07-09 19:36:51 +0000 |
| commit | 4b57d27255e0d66aba6171a931e5bd041d9a6ed1 (patch) | |
| tree | 9e85a3258d8e90fa8801de94fdbd7a7fefba0510 | |
| parent | changed version to 19990709 (diff) | |
| download | rtems-4b57d27255e0d66aba6171a931e5bd041d9a6ed1.tar.bz2 | |
Added information on the workspace versus heap.
| -rw-r--r-- | doc/FAQ/debug.t | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/FAQ/debug.t b/doc/FAQ/debug.t index 90d923af71..242e677838 100644 --- a/doc/FAQ/debug.t +++ b/doc/FAQ/debug.t @@ -13,6 +13,11 @@ The questions in this category are hints that can ease debugging. @section How do I determine how much memory is left? First there are two types of memory: RTEMS Workspace and Program Heap. +The RTEMS Workspace is the memory used by RTEMS to allocate control +structures for system objects like tasks and semaphores, task +stacks, and some system data structures like the ready chains. +The Program Heap is where "malloc'ed" memory comes from. + Both are essentially managed as heaps based on the Heap Manager in the RTEMS SuperCore. The RTEMS Workspace uses the Heap Manager directly while the Program Heap is actually based on an RTEMS Region |