VirtualBox

Changes between Version 2 and Version 3 of Ticket #9659, comment 21


Ignore:
Timestamp:
04/30/13 09:56:30 (12 months ago)
Author:
Petr Vones
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9659, comment 21

    v2 v3  
    55I have also tried to insert System.Diagnostics.Debugger.Break() before the M1() method call instead of setting a breakpoint in Visual Studio and it worked fine. It seems to be as a thread synchronization (CPU cache coherence ?) issue between the debugger process (Visual Studio) and debugged one. Still, it is weird that only debugged process is affected and there are no similar issues with multithreaded code in general. Maybe there is something in VirtualBox that handles processes with 'debugger attached flag' in a different way. 
    66 
     7Does all of you run VirtualBox on Windows host ? Any chance to check the issue on different one ? 
     8 
    79I think there isn't anything else to try. We have to wait if the issue gets attention and will be investigated. If not, the only solution is probably to move to different vitualization software because such serious bug makes software development almost impossible. 

www.oracle.com
ContactPrivacy policyTerms of Use