|
From: | Jimen.Ching |
Subject: | RE: Stack usage in glibc (vfprintf) |
Date: | Tue, 17 Oct 2000 10:15:56 -1000 |
"Ulrich Drepper" <address@hidden> writes:
>"Jimen.Ching" <address@hidden> writes:
>> Should a library function take this much space off the stack?
>Why not? This is no embedded C library, we measure RAM size in 64MB
>steps.
When working with threads, often you can specify the exact amount of
stack space the thread needs. I have calculated stack usage by my thread,
down to the nearest 1024 bytes. But as soon as I make a simple call to
sprintf, the stack is blown away.
If such problems are common place, I would like to know the stack requirements
of all glibc API. What other bugs are lurking in my code because the glibc
API is a stack hog? There is no easy way for me to verify unless I look at
the source code for every glibc API.
As for embedded usage. I am not using glibc for an embedded system right
now. But isn't glibc used by the Embedded Linux? If so, I am sure those
users would run into similar problems.
--jc
--
address@hidden Adtech, Inc. (808) 734-3300
[Prev in Thread] | Current Thread | [Next in Thread] |