Filed under https://bugzilla.xamarin.com/show_bug.cgi?id=8905
Thanks. On Wed, Dec 12, 2012 at 5:06 AM, Andrii Nakryiko <andrii.nakry...@gmail.com>wrote: > From readme: > > mono-jit-crash-repro > ==================== > > Reproduction of problems with Mono JIT crashing. > > To run reproduce, compile the solution and run **run.sh** script which > will start the binary in a loop until the program crashes. It usually > doesn't take long for crash or segmentation fault to occur, though it can > take up to few thousands runs. > > There are two classes that reproduces two bugs: > > * **ReproJitCrash.cs** reproduces JIT crash most of the times. Rarely it > also causes segmentation fault without any stack traces. > * **ReproSegFault.cs** reproduces segmenation fault with no stack trace > (as mentioned previously). > > The only difference between those two cases is in using *struct* vs > *class* with **using** statement (see LockReleaserStruct/LockReleaserClass). > > Also, it seems essential to have Monitor.Enter/Monitor.Exit, without them > it's not reproducible (or at least I didn't have patience to wait for crash > to happen). > > Hope that helps to identify and fix the problem. >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
