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=79462 --- shadow/79462 2006-10-17 08:14:19.000000000 -0400 +++ shadow/79462.tmp.25038 2006-10-19 06:18:58.000000000 -0400 @@ -1,16 +1,16 @@ Bug#: 79462 -Product: Mono: Compilers +Product: Mono: Runtime Version: 1.1 OS: unknown OS Details: Ubuntu 6.06/6.10 AMD64 Status: REOPENED Resolution: Severity: Unknown Priority: Major -Component: C# +Component: misc AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: Summary: gmcs dies with "failed to create shadow copy" @@ -119,6 +119,29 @@ Contributors. www.mono-project.com TLS: __thread GC: Included Boehm (with typed GC) SIGSEGV: normal Disabled: none + +------- Additional Comments From [EMAIL PROTECTED] 2006-10-19 06:18 ------- +I've played around with mono/metadata/appdomain.c a bit. + +'make_shadow_copy' (which was introduced in r64262) tries to create a +temporary file using 'mono_mkstemp'. The pathname is assembled by +'g_build_filename' which accepts a base and a NULL terminated list of +path components. The base is the DynamicBase of the Mono domain +(domain->setup->dynamic_base). Because string is NULL (at least the +return value of 'mono_string_to_utf8') 'g_build_filename' also returns +NULL. This is why mono_mkstemp fails! + +Is it the DynamicBase which is not initialized correctly? Is it +ignored when creating new domains? Can it be configured somewhere? I +actually don't know and do not have the time to investigate any further. + +Could anybody please have a look what is going wrong there? Would be +great! I currently can only use the Mono environment here with a very +ugly patch. + +Thanks! + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
