stack depth problem

  • Thread starter Thread starter PJ6
  • Start date Start date
P

PJ6

I have an algorithm that processes data recursively. When I'm testing it
works fine, but when I feed it data from the actual application, I get
"stack overflow". What bothers me is that the data my recursive processor is
seeing in production is identical to the test data; the only difference is
that now the processor must go deeper into an object model to get the values
with which it is working. I trace things through, there is no out of control
recursion. I've never seen this before, but the stack just craps out on a
legitimate path of execution. Not enough room. Before I rewrite my
processor, I'd like to know, is there a way of increasing stack depth?

I'm probably going to have dump the recursion since data can change... so
this question is more academic than anything else.

Paul
 
PJ6 said:
I have an algorithm that processes data recursively. When I'm testing it
works fine, but when I feed it data from the actual application, I get
"stack overflow". What bothers me is that the data my recursive processor
is seeing in production is identical to the test data; the only difference
is that now the processor must go deeper into an object model to get the
values with which it is working. I trace things through, there is no out of
control recursion. I've never seen this before, but the stack just craps
out on a legitimate path of execution. Not enough room. Before I rewrite my
processor, I'd like to know, is there a way of increasing stack depth?
Click to expand...

Yes, there is. You can use the STACKSIZE in a module definition file or the
/STACK:n where n is the size in bytes of the maximum amount of stack you
expect to use.

Regards,
Will
 
PJ6 said:
I have an algorithm that processes data recursively. When I'm testing
it works fine, but when I feed it data from the actual application, I
get "stack overflow". What bothers me is that the data my recursive
processor is seeing in production is identical to the test data; the
only difference is that now the processor must go deeper into an
object model to get the values with which it is working. I trace
things through, there is no out of control recursion. I've never seen
this before, but the stack just craps out on a legitimate path of
execution. Not enough room. Before I rewrite my processor, I'd like
to know, is there a way of increasing stack depth?
I'm probably going to have dump the recursion since data can
change... so this question is more academic than anything else.
Click to expand...

You can increase the stack size for any threads that you create by passing a
larger stack size to CreateThread (or _beginthreadex). For the main entry
point of the application, you can increase the stack size using the linker
option /STACK:size_in_bytes when the EXE is linked (or with the STACKSIZE
directive in a .DEF file, or by using EDITBIN on the EXE after linking).
Note that if you're not building the EXE, the only recourse you have is to
create a new thread with the larger size.

I'd agree though - if you're using up a 1Mb stack, you probably need to
think about a non-recursive approach.

-cd
 
Back
Top