[Mono-bugs] [Bug 466505] New: Debugger not stopping on domains using shadow copy

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=466505


           Summary: Debugger not stopping on domains using shadow copy
    Classification: Mono
           Product: Mono: Debugger
           Version: 2.2.x
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: backend
        AssignedTo: martin at novell.com
        ReportedBy: lluis at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


When setting a breakpoint in a method that runs in a secondary appdomain, the
debugger doesn't stop in the breakpoint if the domain is using Shadow Copy to
load the assemblies.

Here is a test case. Set a breakpoint in any line of the Run method. The
debugger won't stop. If the domain is created with no shadow copy, it works
fine.

using System;
using System.IO;
using System.Reflection;
using System.Diagnostics;

using System.Security.Policy;

using System.Collections;
using System.Collections.Generic;

class App
{
    public static void Main (string[] args)
    {
        Console.WriteLine (typeof(App).Assembly.CodeBase);
        AppDomainSetup setup = new AppDomainSetup();

        setup.ShadowCopyFiles = "true";

        setup.ShadowCopyDirectories = Path.GetDirectoryName
(typeof(App).Assembly.Location);

        setup.CachePath = "cache";

        Evidence baseEvidence = AppDomain.CurrentDomain.Evidence;

        Evidence evidence = new Evidence(baseEvidence);

        AppDomain runnerDomain = AppDomain.CreateDomain ("other", evidence,
setup);

        runnerDomain.DoCallBack (Run);
    }

    static void Run ()
    {
        Console.WriteLine ("Domain: " + AppDomain.CurrentDomain.FriendlyName);
        Assembly asm = typeof(App).Assembly;
        Console.WriteLine (asm.CodeBase);
    }
}

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.