System.Diagnost ics.StackTrace is wrong sometims

[Zytan]

I use System.Diagnost ics.StackTrace to get the stack trace of the
current function, to print out the function's name to the log, and
sometimes it shows that a function that doesn't even write to the log
is what is writing to the log. This just can't be, so
System.Diagnost ics.StackTrace must be returning the wrong information
(from another thread, i suppose).

Is this normal, or expected? Can it be reliable?

Zytan

[Zytan]

Ah. Is it possible that the automatic function inlining built into C# is

causing your function to just "disappear" ? It won't show up in a stack
trace if it no longer exists.

I've just checked, and for that to happen, it needs to miss TWO
functions in the chain, but they ARE in the same call stack. And
these functions are not small functions! But, at least this explains
what is happening...

Unfortunately, it makes the call stack rather useless to determine
what the current function is...

Zytan

[Zytan]

Can you post a short sample of code that displays a correct stack trace when

compiled as Debug and an incorrect stack trace when compiled as Release?

static void Main(string[] args)
{
MyFunc();
Console.ReadKey (false);
}

public static void MyFunc()
{
Console.WriteLi ne(Program.GetC allStack());
}

public static string GetCallStack()
{
System.Diagnost ics.StackTrace callStack = new
System.Diagnost ics.StackTrace( );
string s = "";
int index = 0;
while (true)
{
System.Diagnost ics.StackFrame frame =
callStack.GetFr ame(index);
if (frame == null) break;
System.Reflecti on.MethodBase method = frame.GetMethod ();

if (index 0) s = " --" + s;
s = method.Declarin gType.Name + "." + method.Name + "()" + s;
index++;
}
return (s);
}

Zytan

[Zytan]

Ah. Is it possible that the automatic function inlining built into C# is

causing your function to just "disappear" ? It won't show up in a stack
trace if it no longer exists.

Pete, I think I solved the issue.

My functions were large, so they were NOT being deleted from the call
stack, but..... my WriteFunction() function which my function call is
tiny. AND, it has to take measures to not print ITSELF when its
caller is asking "who am I?". So, it counts to skip itself where it
expects to be in the call stack. In release mode, since it is so
small, it gets ejected from the call stack, and thus when it chooses
to skip itself, it's really skipping the function name that I wanted!
And, furthermore, because this WriteFunction() is a wrapper, and not
the real deal, they are likely BOTH ejected from the release call
stack, which explains why TWO of my treasured functions are missing
from the display!

NOW, for the solution to this mess...

Zytan