[Mono-bugs] [Bug 78724][Nor] New - Assembly.GetTypes(bool) broken on Dynamic Assemblies

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Jun 28 18:55:39 EDT 2006

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 rektide at voodoowarez.com.


--- shadow/78724	2006-06-28 18:55:38.000000000 -0400
+++ shadow/78724.tmp.4904	2006-06-28 18:55:38.000000000 -0400
@@ -0,0 +1,95 @@
+Bug#: 78724
+Product: Mono: Class Libraries
+Version: 1.1
+OS: GNU/Linux [Other]
+OS Details: Debian Sid & Etch
+Status: NEW   
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: rektide at voodoowarez.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Assembly.GetTypes(bool) broken on Dynamic Assemblies
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+Honestly, the problem is booish, the Boo interactive interpretter, no 
+longer works on Mono.  Something in Mono's Assembly reflection degenerated 
+and booish no longer works.  The call fails when an 
+System.Reflection.Assembly object calls a GetTypes(bool) method, where the 
+assembly reflection object is a dynamic assembly.  A trivial test case is 
+still needed.
+Steps to reproduce the problem:
+1. install boo
+2. run booish
+3. input:
+class foo:
+  a as int
+print "x"
+Actual Results:
+Got a SIGSEGV while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+in (wrapper managed-to-native) System.Reflection.Assembly:GetTypes 
+(bool) <0x4>
+in (wrapper managed-to-native) System.Reflection.Assembly:GetTypes 
+(bool) <0xffffffe4>
+in System.Reflection.Assembly:GetTypes () <0xc>
+(System.Reflection.Assembly) <0x2f>
+ () <0xb9>
+in Boo.Lang.Compiler.Steps.InitializeNameResolutionService:Run () <0x44>
+in Boo.Lang.Compiler.CompilerPipeline:RunStep 
+(Boo.Lang.Compiler.CompilerContext,Boo.Lang.Compiler.ICompilerStep) <0x4d>
+in Boo.Lang.Compiler.CompilerPipeline:Run 
+(Boo.Lang.Compiler.CompilerContext) <0xef>
+in Boo.Lang.Compiler.BooCompiler:Run 
+(Boo.Lang.Compiler.Ast.CompileUnit) <0x6e>
+in (wrapper remoting-invoke-with-check) Boo.Lang.Compiler.BooCompiler:Run 
+(Boo.Lang.Compiler.Ast.CompileUnit) <0xfffff5a6>
+in Boo.Lang.Interpreter.AbstractInterpreter:EvalCompileUnit 
+(Boo.Lang.Compiler.Ast.CompileUnit) <0x326>
+in Boo.Lang.Interpreter.AbstractInterpreter:EvalCompilerInput 
+(Boo.Lang.Compiler.ICompilerInput) <0x5d>
+in Boo.Lang.Interpreter.AbstractInterpreter:Eval (string) <0xfa>
+in Boo.Lang.Interpreter.InteractiveInterpreter:InternalLoopEval 
+(string) <0x20>
+in Boo.Lang.Interpreter.InteractiveInterpreter:ConsoleLoopEval () <0x8d>
+in BooishModule:Main (string[]) <0x1a4>
+in (wrapper runtime-invoke) 
+System.Object:runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xb1a327>
+Native stacktrace:   
+        /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0xeb) [0xa7d7f92b]
+        /usr/lib/libmono.so.0 [0xa7d4070d]
+Expected Results:
+How often does this happen? 
+Always in linux.
+Additional Information:
+This problem appears to afflict all Mono using Boo'ites.  We've chatted it 
+up in the IRC channel, and it is indeed universal: Mono has stopped 
+running booish.

More information about the mono-bugs mailing list