Hello, Is there a way to monitor the current stack space within a program? And, as a bonus, the heap and shared memory? I found getrusage() in <sys/resource.h> but the linker complains that there is no object. -- jimoe (at) sohnen-moe (dot) com
James Moe wrote: > Hello, > Is there a way to monitor the current stack space within a program? And, > as a bonus, the heap and shared memory? The best way to monitor stack usage is by coloring (memset()) the stack and check how much of it is untouched. You can get the stack top/bottom addresses from DosGetInfoBlocks(&pTib, &pPib); pTib->tib_...stack. I don't quite recall if there is a heap api for querying the amount memory it currently uses. grep -e 'heap.*stat' might find something... As for shared memory, there you have to ask OS/2, which means using the kernel debugger or Theseus (former is difficult, the latter I'm not very familiar with I'm afraid). > I found getrusage() in <sys/resource.h> but the linker complains that > there is no object. I don't think we've got a working getrusage() yet. Kind Regards, knut
Knut St. Osmundsen wrote: > James Moe wrote: >> Hello, >> Is there a way to monitor the current stack space within a program? And, >> as a bonus, the heap and shared memory? > > The best way to monitor stack usage is by coloring (memset()) the stack > and check how much of it is untouched. You can get the stack top/bottom > addresses from DosGetInfoBlocks(&pTib, &pPib); pTib->tib_...stack. > That's good. Is there a simple way to get the value of the Stack Pointer? All I'd need is ESP. I seem to recall an _asm() directive. Is that supported by gcc? -- jimoe (at) sohnen-moe (dot) com
In <4579BFDA.2050707 <at> sohnen-moe.com>, on 12/08/06 at 12:41 PM, James Moe <jimoe <at> sohnen-moe.com> said: > Is there a simple way to get the value of the Stack Pointer? No need for _asm() here. Just take the address of the last local variable. Regards, Steven -- -- ---------------------------------------------------------------------- "Steven Levine" <steve53 <at> earthlink.net> MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) ----------------------------------------------------------------------
Steven Levine wrote:
> In <4579BFDA.2050707 <at> sohnen-moe.com>, on 12/08/06
> at 12:41 PM, James Moe <jimoe <at> sohnen-moe.com> said:
>
>> Is there a simple way to get the value of the Stack Pointer?
>
> No need for _asm() here. Just take the address of the last local
> variable.
Another option is to do a tiny dynamic stack allocation:
void *pvTopOfStack = alloca(1);
The inline assembly for reading ESP goes like this:
__asm__ __volatile__ ("movl %0,%%esp", "=r" (pvTopOfStack));
If you are going to color (memset) the stack, you have to add a safety
area between the current stack pointer and where you start (stop
actually considering the stack direction) the coloring. That goes for
all three methods.
Kind Regards,
knut
In <4579A529.3070903 <at> anduin.net>, on 12/08/06 at 06:47 PM, "Knut St. Osmundsen" <bird <at> anduin.net> said: >I don't quite recall if there is a heap api for querying the amount >memory it currently uses. grep -e 'heap.*stat' might find something... It looks like ustats() might do the job. >Theseus (former is difficult, the latter I'm not very >familiar with I'm afraid). It's pretty easy with Theseus for a running app. Select the app on the main gui window. Then it's Process->Memory Utilization. Regards, Steven -- -- ---------------------------------------------------------------------- "Steven Levine" <steve53 <at> earthlink.net> MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) ----------------------------------------------------------------------
In <4579E384.2010301 <at> anduin.net>, on 12/08/06 at 11:13 PM, "Knut St. Osmundsen" <bird <at> anduin.net> said: >If you are going to color (memset) the stack, you have to add a safety >area between the current stack pointer and where you start (stop >actually considering the stack direction) the coloring. That goes for >all three methods. Also when coloring the stack for the main thread, it's a good idea to start at the top of the area to be colored and work downward. Regards, Steven -- -- ---------------------------------------------------------------------- "Steven Levine" <steve53 <at> earthlink.net> MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) ----------------------------------------------------------------------
#133: _SC_PAGESIZE missing in sysconf()
--------------------+-------------------------------------------------------
Reporter: cinc | Owner: bird
Type: defect | Status: new
Priority: normal | Milestone:
Component: libc | Version: 0.6.1
Severity: normal | Keywords: sysconf _SC_PAGESIZE
--------------------+-------------------------------------------------------
The sysconf() function doesn't implement the _SC_PAGESIZE (and
_SC_PAGE_SIZE) parameters. This breaks GLIB 2.12.4 compilation (a
workaround is easy, though).
--
Ticket URL: <http://svn.netlabs.org/libc/ticket/133>
kLIBC <http://svn.netlabs.org/libc>
kLIBC
Steven Levine wrote: > >> Is there a simple way to get the value of the Stack Pointer? > > No need for _asm() here. Just take the address of the last local > variable. > How easy! Works a treat. Thanks. -- jimoe (at) sohnen-moe (dot) com
RSS Feed4 | |
|---|---|
8 | |
3 | |
3 | |
9 | |
4 | |
1 | |
3 | |
2 | |
37 | |
39 | |
17 | |
41 | |
29 | |
28 | |
31 | |
79 | |
67 | |
9 | |
11 | |
11 | |
38 | |
9 | |
6 | |
14 | |
11 | |
2 | |
15 | |
8 | |
6 | |
20 | |
22 | |
58 | |
90 | |
72 | |
15 | |
13 | |
9 | |
20 | |
11 | |
33 | |
69 | |
82 | |
29 | |
4 | |
5 | |
3 | |
9 | |
67 | |
7 | |
28 | |
8 |
