[Mono-bugs] [Bug 66872][Nor] New - mono --trace=program segfaults
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 27 Sep 2004 00:51:26 -0400 (EDT)
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 peter@newton.cx.
http://bugzilla.ximian.com/show_bug.cgi?id=66872
--- shadow/66872 2004-09-27 00:51:26.000000000 -0400
+++ shadow/66872.tmp.12071 2004-09-27 00:51:26.000000000 -0400
@@ -0,0 +1,32 @@
+Bug#: 66872
+Product: Mono: Runtime
+Version: unspecified
+OS:
+OS Details:
+Status: NEW
+Resolution:
+Severity:
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com
+ReportedBy: peter@newton.cx
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: mono --trace=program segfaults
+
+If you try to trace with the CVS runtime, you get a segfault. This is
+because in driver.c we have:
+
+
+735: mono_jit_trace_calls = mono_trace_parse_options (assembly, trace_options);
+....
+796: assembly = mono_assembly_open (aname, NULL);
+
+That is, the trace_spec structure is always initialized with assembly =
+NULL, causing a segfault in some situations.
+
+Solution is obviously to reorder the calls, but I am not familiar with
+runtime internals so I haven't tried to cook up a patch for fear of causing
+weird side effects.