"Søren Johansen" <soerenjohansen171@hotmail.com> wrote in message
news:OrxnRqqUDHA.2112@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I am getting a stack overflow exception. I was wondering how to to debug
> this situation with vc.
> I know that the problem is not based on (unintended or intended) recursion
> and the call stack at the time of the exception is rather small. Thus,
there
> must be some variable declared on the stack that takes up a lot of memory.
> How can I find this? I thought about setting a data-breakpoint in the end
of
> the stack but I don't know what this address would be.

"Søren Johansen" <soerenjohansen171@hotmail.com> wrote in message
news:OadzNsOVDHA.484@TK2MSFTNGP09.phx.gbl...
> > If it's reproducable, just put a breakpoint at the beginning of the
> function
> > and track all automatic variables that are created. A class with many
> value
> > members can also be a problem.
> >
> > class {
> > public:
> > char a[1000000];
> > }
>
> Well it is (reproductable), but the final function called does not
allocate
> major variables. In fact, I don't see any of the functions on the call
stack
> with any variables of significance. Which is why I think that you are
> right - there is a class somewhere that contains some large member. But
how
> can I track this sort of thing down?
>
>

> If it's reproducable, just put a breakpoint at the beginning of the
function
> and track all automatic variables that are created. A class with many
value
> members can also be a problem.
>
> class {
> public:
> char a[1000000];
> }