StackFrame is inconsistent in Debug version and Release version

[HCF_15]

Hi all,

I have a small piece of code to use StackFrame to GetMethod, I found it is
inconsistent in Debug version and Release version, is there anything I am
doing wrong?
Here is code, build in Debug and Release version, you will get different
results.
My env. is VS 2005 on XP with SP2.

Thanks in advanced.

HCF
---------------------------------------------------

using System;
using System.Diagnost ics;
using System.Reflecti on;

class Example
{
private static string GenerateFuncNam e()
{
StackFrame sf = new StackFrame(2);
MethodBase mb = sf.GetMethod();
if ( mb != null )
return mb.DeclaringTyp e.Name + "." + mb.Name;
else
return "Unknown FuncName";
}

private static string getInfo()
{
string info = GenerateFuncNam e();
return info;
}

static void Main()
{
Console.WriteLi ne(getInfo());
return;
}
}

[Barry Kelly]

"HCF_15" <hc****@hotmail .com> wrote:

I have a small piece of code to use StackFrame to GetMethod, I found it is
inconsistent in Debug version and Release version, is there anything I am
doing wrong?

Debug mode inhibits CLR optimizations. One CLR optimization inhibited is
inlining. What you are seeing is the result of method inlining.

From the StackFrame documentation (I know, it's a different class):

---8<---
StackTrace might not report as many method calls as expected, due to
code transformations that occur during optimization.
--->8---

-- Barry

[HCF_15]

Got it, Thanks Barry.

"Barry Kelly" <ba***********@ gmail.com> wrote in message
news:6h******** *************** *********@4ax.c om...

"HCF_15" <hc****@hotmail .com> wrote:

I have a small piece of code to use StackFrame to GetMethod, I found it
is
inconsistent in Debug version and Release version, is there anything I am
doing wrong?

Debug mode inhibits CLR optimizations. One CLR optimization inhibited is
inlining. What you are seeing is the result of method inlining.

From the StackFrame documentation (I know, it's a different class):

---8<---
StackTrace might not report as many method calls as expected, due to
code transformations that occur during optimization.
--->8---

-- Barry