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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78125 --- shadow/78125 2006-05-02 07:48:46.000000000 -0400 +++ shadow/78125.tmp.22740 2006-05-02 20:32:08.000000000 -0400 @@ -205,6 +205,24 @@ SCG-based version of test case ------- Additional Comments From [EMAIL PROTECTED] 2006-05-02 07:48 ------- Miguel, why did you reassign the closed bug to me, it was RESOLVED FIXED in Bugzilla ? + +------- Additional Comments From [EMAIL PROTECTED] 2006-05-02 20:32 ------- +I had mistakenly closed the bug, but I'd reopened it, above. + +This bug looks like a memory corruption issue that's not easy to +expose as a segfault (the 5/1 attachment, for example, crashes under +--trace on amd64 but not under x86). To repro it I'd suggest one of +the following routes: + - Running the first HashCrash.cs attachment under 1.1.13.2, + - _or_, running the BigTest.exe application that I've attached. I +can provide the source, but it's not a small app; unfortunately it's +the only one I've found that consistently causes the runtime to +segfault on various architectures and versions of mono. + +This bug is important to me (I'm blocking on it), so I'd be happy to +provide whatever information you need and/or to spend time debugging +it, if someone can point me in the right direction. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
