[Mono-bugs] [Bug 352377] New: gmcs fails to compile asp. net assembly when called from xsp2 debugged by mdb
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Tue Jan 8 12:59:24 EST 2008
https://bugzilla.novell.com/show_bug.cgi?id=352377
Summary: gmcs fails to compile asp.net assembly when called from
xsp2 debugged by mdb
Product: Mono: Compilers
Version: 1.2.6
Platform: 32bit
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: C#
AssignedTo: mono-bugs at ximian.com
ReportedBy: dobos_s at ibcnet.hu
QAContact: mono-bugs at ximian.com
Found By: ---
xsp2 generates temporary assembly and tries to compile it with gmcs.
When xsp2 is running under mdb, the compilation fails, the client gets error:
Server Error in '/' Application
--------------------------------------------------------------------------------
Compiler failed to produce the assembly. Stderr='', Stdout=''
Description: Error processing request.
Error Message: HTTP 500. System.Exception: Compiler failed to produce the
assembly. Stderr='', Stdout=''
Stack Trace:
System.Exception: Compiler failed to produce the assembly. Stderr='', Stdout=''
at Mono.CSharp.CSharpCodeCompiler.CompileFromFileBatch
(System.CodeDom.Compiler.CompilerParameters options, System.String[] fileNames)
[0x00252] in
/CLX/t2/mono-1.2.6/mcs/class/System/Microsoft.CSharp/CSharpCodeCompiler.cs:235
at Mono.CSharp.CSharpCodeCompiler.CompileAssemblyFromFileBatch
(System.CodeDom.Compiler.CompilerParameters options, System.String[] fileNames)
[0x00011] in
/CLX/t2/mono-1.2.6/mcs/class/System/Microsoft.CSharp/CSharpCodeCompiler.cs:138
at Mono.CSharp.CSharpCodeCompiler.CompileFromDomBatch
(System.CodeDom.Compiler.CompilerParameters options,
System.CodeDom.CodeCompileUnit[] ea) [0x00100] in
/CLX/t2/mono-1.2.6/mcs/class/System/Microsoft.CSharp/CSharpCodeCompiler.cs:371
at Mono.CSharp.CSharpCodeCompiler.CompileAssemblyFromDomBatch
(System.CodeDom.Compiler.CompilerParameters options,
System.CodeDom.CodeCompileUnit[] ea) [0x00011] in
/CLX/t2/mono-1.2.6/mcs/class/System/Microsoft.CSharp/CSharpCodeCompiler.cs:120
at Mono.CSharp.CSharpCodeCompiler.CompileAssemblyFromDom
(System.CodeDom.Compiler.CompilerParameters options,
System.CodeDom.CodeCompileUnit e) [0x00000] in
/CLX/t2/mono-1.2.6/mcs/class/System/Microsoft.CSharp/CSharpCodeCompiler.cs:110
at System.Web.Compilation.CachingCompiler.Compile
(System.Web.Compilation.BaseCompiler compiler) [0x00085] in
/CLX/t2/mono-1.2.6/mcs/class/System.Web/System.Web.Compilation/CachingCompiler.cs:96
at System.Web.Compilation.BaseCompiler.GetCompiledType () [0x001aa] in
/CLX/t2/mono-1.2.6/mcs/class/System.Web/System.Web.Compilation/BaseCompiler.cs:540
at System.Web.Compilation.AspGenerator.GetCompiledType () [0x00055] in
/CLX/t2/mono-1.2.6/mcs/class/System.Web/System.Web.Compilation/AspGenerator.cs:290
at System.Web.UI.ApplicationFileParser.GetCompiledApplicationType
(System.String inputFile, System.Web.HttpContext context) [0x0000f] in
/CLX/t2/mono-1.2.6/mcs/class/System.Web/System.Web.UI/ApplicationFileParser.cs:57
at System.Web.HttpApplicationFactory.InitType (System.Web.HttpContext
context) [0x0007d] in /CLX/t2/mono-1.2.6/mcs/class/System
After doing some hacks I found, that gmcs wont start, instead mono prints
something about Trace/Breakpoint trap and exits.
So Mono.CSharp.CSharpCodeCompiler.CompileFromFileBatch fails, because the
outputAssembly wont exists.
My solution:
Insert "unset MONO_INSIDE_MDB" before exec line into gmcs batch file.
--
Configure bugmail: https://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.
More information about the mono-bugs
mailing list