http://bugzilla.novell.com/show_bug.cgi?id=565923
http://bugzilla.novell.com/show_bug.cgi?id=565923#c0 Summary: runtime always SEGFAULT booc.exe upon exit and reports exit code 139 Classification: Mono Product: Mono: Runtime Version: 2.6.x Platform: Other OS/Version: Mac OS X 10.5 Status: NEW Severity: Critical Priority: P5 - None Component: misc AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: --- Blocker: Yes The latest mono release (2.6) always SEGFAULT booc.exe when System.Reflection.Emit is used. Even though booc.exe completes successfully the runtime will always report exit 139 because of said SEGFAULT. With a clean mono 2.6 setup do the following: prompt$ cd /tmp prompt$ cat > test.boo print "boo!" prompt$ booc test.boo; echo $? Boo Compiler version 0.9.2.3383 (tarball Mon Dec 14 15:51:57 MST 2009) /Library/Frameworks/Mono.framework/Home/bin/booc: line 6: 12158 Segmentation fault env /Library/Frameworks/Mono.framework/Versions/2.6/bin/mono $MONO_OPTIONS /Library/Frameworks/Mono.framework/Versions/2.6/lib/boo/booc.exe $BOOC_OPTIONS "$@" 139 Notice that booc.exe successfully compiled test.boo into test.exe: prompt$ mono test.exe boo! It's probably something about the cleanup of System.Reflection or System.Reflection.Emit related structures. This is completely critical because for it renders the boo compiler almost unusable. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
