Bug 11547 – 'Stop'ing a 32bit Mago vibe.d debug session throws annoying error dialog

Status
RESOLVED
Resolution
FIXED
Severity
normal
Priority
P2
Component
visuald
Product
D
Version
D2
Platform
x86
OS
Windows
Creation time
2013-11-18T22:46:00Z
Last change time
2013-12-01T21:09:46Z
Assigned to
nobody
Creator
turkeyman

Comments

Comment #0 by turkeyman — 2013-11-18T22:46:59Z
When I debug my 32bit vibe.d app using Mago, hitting 'stop' throws an annoying error dialog that constantly interrupts my workflow. Since web-dev is a highly iterative process, I can see this box numerous times per minute, very frustrating after a few hours/days. "Unable to stop debugging. Operation not supported. Unknown error: 0x800400c3" Visual Studio debugger doesn't do this.
Comment #1 by r.sagitario — 2013-11-19T00:23:31Z
I've noticed this, too. I think it doesn't happen with VS2008, but newer ones.
Comment #2 by turkeyman — 2013-11-19T02:53:49Z
Mmm, I haven't been able to affect it fiddling with various options.
Comment #3 by r.sagitario — 2013-11-29T02:39:28Z
Comment #4 by turkeyman — 2013-11-29T06:48:07Z
(In reply to comment #3) > should be fixed with mago 0.9 in > https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.38beta1 I'm still having the problem. What was the fix?
Comment #5 by r.sagitario — 2013-11-30T00:31:43Z
> I'm still having the problem. What was the fix? It is actually now suppressing an error when VS wants the debug engine to kill the process, but it is already dead. It guess the patch wasn't good enough when doing this on a larger application. I changed it slightly and replaced the installer by a beta1a at the same location.
Comment #6 by turkeyman — 2013-12-01T21:08:35Z
(In reply to comment #5) > > I'm still having the problem. What was the fix? > > It is actually now suppressing an error when VS wants the debug engine to kill > the process, but it is already dead. > > It guess the patch wasn't good enough when doing this on a larger application. > I changed it slightly and replaced the installer by a beta1a at the same > location. Fixed. Thanks again! :)