https://bugzilla.novell.com/show_bug.cgi?id=669621
https://bugzilla.novell.com/show_bug.cgi?id=669621#c0 Summary: Debug Tracing skips some property set() statements. Classification: Mono Product: MonoDroid Version: SVN Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Debugger AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.84 Safari/534.13 When tracing, many property set() statements are not properly traced by the debugger. In some cases, tracing successfully enters the set() function of the property, but in some other cases, it does not enter it and appears to skip it. Putting breakpoints inside the set() function of the property does not work, making believe the code is not executed at all. However, adding some System.Diagnostics.Debug.WriteLine() statements shows the code gets executed, it just cannot be properly traced, and breakpoints are ignored. Reproducible: Always Steps to Reproduce: My solution is quite small, with only a few classes coming from class library assemblies. I am guessing reproducing the problem should not be too hard in a complex project. Actual Results: The tracer does not always get inside the set() functions of the properties when hitting F11 on it. Sometimes it does, other times it just doesn't. It is always the same properties that work, and the same properties that don't work, from what I could observe. Expected Results: The debug tracer should enter the set() function of all the properties. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
