Re: getting bad values from calls to GetThreadCallStack()

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: fbcome@xxxxxxxxxxxx
Date: Sun, 9 Mar 2008 18:43:08 -0700 (PDT)

CallSnapshot.dwReturnAddr holds the return address not the entry
address of the caller function.

For example:
int foo()
{
...
foo2(); //the return address of foo2() points to the next
instruction: "i++", not the entry address of foo()
i++;
...
}
.

Prev by Date: building error in OSdesign with vs2005 and wince6.0
Next by Date: Re: getting bad values from calls to GetThreadCallStack()
Previous by thread: building error in OSdesign with vs2005 and wince6.0
Next by thread: Re: getting bad values from calls to GetThreadCallStack()
Index(es):
- Date
- Thread

Relevant Pages

Evaluation order of assignment statement
... int array; ... Microsoft Visual C prints: foo2, foo3, foo1. ...
(comp.lang.c)
Re: Portable replacement
... int greater_or_equal4 ... On my platform, foo1 and foo2 are equivalent. ...
(comp.lang.c)
Re: getting bad values from calls to GetThreadCallStack()
... CallSnapshot.dwReturnAddr holds the return address not the entry ... int foo() ... foo2(); //the return address of foo2points to the next ... address of foo() and smaller than next function's address. ...
(microsoft.public.windowsce.platbuilder)
Re: Portable replacement
... int greater_or_equal4 ... On my platform, ... My claim is that foo2 is portable, while foo1 is not. ...
(comp.lang.c)
Re: More function names, same implementation
... int foo1 ... Is there a way besides #defining? ... you want foo1 and foo2 to be two different names for ... foo2 with no name for the parameter, ...
(comp.lang.c)