|
From: Olly B. <ol...@su...> - 2005-02-19 20:22:56
|
On 2005-02-19, MIchael Harwerth <Mi...@gm...> wrote:
> No, nothing at all. It is a plain old single-thread console app... Valgrind
> warns - if called with the -v option -
>
> Warning: client switching stacks? %esp: 0x52BFE35C --> 0x5290FDD0
>
> That may be the reason why, the stack pointer grows a large amount, but I
> don't know why.
Do you declare any large automatic arrays?
something like:
int func(void) {
int bigarray[1000000];
func2();
}
Valgrind has a heuristic to try to detect stack switches - this warning
means it fired. If you aren't switching stacks, something like the
above is likely to be the reason (and may explain crashes on platforms
which aren't able to allocate large amounts of extra stack on demand).
Cheers,
Olly
|