Re: SetWindowPos causing crash
"Doug Harrison [MVP]" <dsh@mvps.org> wrote in message
news:lpvsg3lvcpq2a6up2ufl615bevnl2kdcbt@4ax.com...
On Thu, 11 Oct 2007 12:11:00 -0700, RobKinney1
<mydigitalportal.net@gmail.com.NOSPAMPLEASE> wrote:
When you say to walk the stack, am I supposed to implement something like
this into my program?
http://www.codeproject.com/threads/StackWalker.asp
I have never done this before and was always wondering how to do it.
I am going to try that meanwhile and see if I can get it to print out to a
file.
Oh no, I just meant to open the call stack window in the debugger and
examine it. You can double-click the entries in that window, and the
debugger will take you to the corresponding line in the source code. That
is probably all you need to do to figure out the problem.
--
Doug Harrison
Visual C++ MVP
Just to clarify a little more, Doug is talking about when program crashes,
open the callstack window, (from Debug/Windows menu).
The top of the stack is the last function that was called, and going down
the list you will see the list of functions that were called in order to
arrive at that location in the program. Alot of times it's in a dll without
source, follow the stack backwards to a place with source. Then if you
still can't figure out the problem, post where you traced the problem to.
AliR.