[Mono-bugs] [Bug 77118][Maj] Changed - StackFrame is invalid on
Mono but not in Windows
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Thu Dec 29 14:43:48 EST 2005
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by robertj at gmx.net.
http://bugzilla.ximian.com/show_bug.cgi?id=77118
--- shadow/77118 2005-12-29 07:35:34.000000000 -0500
+++ shadow/77118.tmp.22026 2005-12-29 14:43:48.000000000 -0500
@@ -1,14 +1,14 @@
Bug#: 77118
Product: Mono: Runtime
Version: 1.1
-OS:
+OS: unknown
OS Details: OS X 10.4.3
Status: NEW
Resolution:
-Severity:
+Severity: Unknown
Priority: Major
Component: JIT
AssignedTo: lupus at ximian.com
ReportedBy: richard.torkar at htu.se
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
@@ -84,6 +84,26 @@
GC: Included Boehm (with typed GC)
SIGSEGV : normal Globalization: normal
And on Windows I use:
Microsoft (R) Visual C# .NET Compiler version 7.10.6001.4
for Microsoft (R) .NET Framework version 1.1.4322
+
+------- Additional Comments From robertj at gmx.net 2005-12-29 14:43 -------
+
+BTW, you should *never* rely on StackFrame. The MS .NET runtime
+uses to inline methods if the app was compiled for RELEASE
+and when the app isn't running by a debugger.
+When this happens, callee and caller are not the expected
+methods. You'll lose your mind, because you cannot debug
+this problem: it doesn't occure while debugging ;-)
+
+If you feel that you cannot live w/out this feature,
+you have to mark each method that will act as a callee
+or caller (in your sample) with
+
+[MethodImpl(MethodImplOptions.NoInlining)]
+
+while giving away some performance.
+
+I bet mono behaves similar.
+
More information about the mono-bugs
mailing list