Dolphin 5.1.4 / Windows Vista / Ctrl-Break acts stuck...

When I am using Dolphin 5.1.4 on Windows Vista and I have to press Ctrl-Break while a debugger is open the system acts like Ctrl-Break is stuck and keeps breaking when I try to open a new browser or debugger. If I close the image and re-open it the problem persists. If I open a different image the problem also occurs. I have to reboot the system to fix it. This has happened a few times. It seems too repeatable for the keys to be actually stuck and re-pressing them does not seem to unstick them. Has anyone else experienced this?

Here is a stack trace:
==========
12:02:07 AM, Friday, November 14, 2008: 'User Interrupt'
Signal>>signal
DevelopmentSessionManager(SessionManager)>>onUserBreak
ProcessorScheduler>>userBreak:
[] in ProcessorScheduler>>vmi:list:no:with:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>vmi:list:no:with:
Association>>=
AssociationSearchPolicy(EqualitySearchPolicy)>>compare:with:
PluggableLookupTable>>findKeyOrNil:
PluggableLookupTable(LookupTable)>>at:put:
[] in PluggableLookupTable(Dictionary)>>atAll:put:
PluggableSet(Set)>>do:
PluggableLookupTable(Dictionary)>>atAll:put:
[] in PackageManager>>getLooseMethods
PluggableLookupTable(LookupTable)>>do:
PackageManager>>getLooseMethods
PackageManager>>looseMethods
PackageManager>>isLooseMethod:
CompiledMethod>>isLoose
[] in UndefinedObject>>{unbound}doIt
NMLVCUSTOMDRAW(NMCUSTOMDRAW)>>evaluateDrawBlock:
ListView>>customDrawSubItem:
ListView(IconicListAbstract)>>nmCustomDraw:
ListView(ControlView)>>nmNotify:
[] in ListView>>nmNotify:
Array(SequenceableCollection)>>at:ifAbsent:
ListView>>nmNotify:
ReferenceView(View)>>wmNotify:wParam:lParam:
ReferenceView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ListView(ControlView)>>defaultWindowProcessing:wParam:lParam:
ListView(ControlView)>>wmPaint:wParam:lParam:
ListView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ListView(ControlView)>>defaultWindowProcessing:wParam:lParam:
ListView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
ProcessorScheduler>>callback:evaluate:
InputState>>wndProc:message:wParam:lParam:cookie:
ListView(ControlView)>>defaultWindowProcessing:wParam:lParam:
ListView(View)>>dispatchMessage:wParam:lParam:
[] in InputState>>wndProc:message:wParam:lParam:cookie:
BlockClosure>>ifCurtailed:
=================

Chris
.

Relevant Pages

  • Re: POP3 Locking up computer
    ... (other threads or GUI controls). ... if they stop responding, they are stuck somewhere. ... Your first step is to use the debugger and find out where your ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Finding a point where a program is stuck in a loop
    ... source code so I'm doing it with the disassembly. ... is there a way to nail down where its getting stuck? ... This is a windows program, and I'm using ollydbg as the debugger. ...
    (comp.lang.asm.x86)
  • Re: POP3 Locking up computer
    ... (other threads or GUI controls). ... I tried async reads, that didn't work. ... if they stop responding, they are stuck somewhere. ... Your first step is to use the debugger and find out where your ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: POP3 Locking up computer
    ... while they are being downloaded nothing else works (other threads or GUI controls). ... I tried async reads, that didn't work. ... Applications don't just stop for no reason; if they stop responding, they are stuck somewhere. ... Your first step is to use the debugger and find out where your application is stuck. ...
    (microsoft.public.dotnet.languages.csharp)