Bug 12565 – IDE cannot launch Mago debugger starting from v0.3.38-beta3

Status
RESOLVED
Resolution
FIXED
Severity
major
Priority
P1
Component
visuald
Product
D
Version
D2
Platform
All
OS
All
Creation time
2014-04-12T11:03:00Z
Last change time
2017-01-24T07:38:14Z
Assigned to
nobody
Creator
verylonglogin.reg

Comments

Comment #0 by verylonglogin.reg — 2014-04-12T11:03:01Z
E.g. when a new console project is created and debugging is started using Mago the only result is a popup dialog with this error message: --- cannot launch debugger on <exe-file-path> hr = 89710016 ---
Comment #1 by verylonglogin.reg — 2014-04-12T11:19:56Z
Since this release (probably because of author's environment reset) all Mago DLLs require Microsoft Visual C++ Redistributable Packages for Visual Studio 2013. So I'd say it is a major documentation issue, as debugging breakage without an appropriate error message or any new requirements in changelog is rather bad.
Comment #2 by r.sagitario — 2014-04-12T11:30:42Z
Ouch, the new runtime should not be necessary or included in the installer. I switched to the new VS after a fatal crash of my SSD, but did not think about the new dependency. Thanks for finding it.
Comment #3 by r.sagitario — 2014-04-15T05:23:38Z
I have rebuilt mago with static linkage of the CRT: https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.38-1
Comment #4 by r.sagitario — 2014-07-03T06:28:45Z
Build fixed in 0.3.38-1
Comment #5 by verylonglogin.reg — 2015-12-02T12:37:02Z
mago commit 59d55f2 [1] reintroduced the issue, this time because of Wow64*Wow64FsRedirection functions which are not present on Windows XP. Opened fixing pull [2]. [1] https://github.com/rainers/mago/commit/59d55f2f99aa57447e1ba4d635eb5ab6d17b6b71 [2] https://github.com/rainers/mago/pull/4
Comment #6 by r.sagitario — 2017-01-24T07:38:14Z
Finally released as part of https://github.com/dlang/visuald/releases/tag/v0.44-beta2 (must heve been in beta1, too)