Bug 11437 – [Mago] No source for step-by-step debugging, only raw assembler.

Status
RESOLVED
Resolution
FIXED
Severity
major
Priority
P2
Component
visuald
Product
D
Version
D2
Platform
All
OS
All
Creation time
2013-11-04T06:54:00Z
Last change time
2014-04-12T09:55:00Z
Assigned to
nobody
Creator
verylonglogin.reg

Comments

Comment #0 by verylonglogin.reg — 2013-11-04T06:54:07Z
Sometimes Mago behaves like there is no debug information available. E.g. in attached testcase if lib_d.lib is removed from linker arguments or placed after GtkD.lib Mago works. Testcase: http://deoma-cmd.ru/files/other/testcases/Mago-error-1.7z
Comment #1 by verylonglogin.reg — 2013-11-04T07:02:48Z
Workaround: Play with the order libraries are passed to the linker. I.e. change the order, press "Step into" (F11), repeat if you still see raw assembler.
Comment #2 by r.sagitario — 2013-11-06T00:40:07Z
I can reproduce the problem. It seems mago is as picky about the order of debug records as recommended by the CV4 documentation (but not made mandatory). As a workaround, the CVPACK utility is supposed to fix that, though I'm unsure if it can still be found somewhere.
Comment #3 by r.sagitario — 2013-11-29T02:39:58Z
Comment #4 by verylonglogin.reg — 2014-01-02T05:31:28Z
(In reply to comment #3) > should be fixed by mago 0.9 in > https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.38beta1 Original testcase works now and everything was fine until some dmd changes. Now it is again no debug information available for most projects I tested, so I use an older dmd version. Testcase: http://deoma-cmd.ru/files/other/testcases/Issue-11437-2.7z
Comment #5 by r.sagitario — 2014-01-03T03:16:59Z
While I have added a workaround in mago for the test case, it is actually an instance of issue 7634.
Comment #6 by r.sagitario — 2014-04-12T09:55:00Z
dmd fixed and workaround now released in Visual D 0.3.38