https://issues.dlang.org/show_bug.cgi?id=14497
--- Comment #3 from Rainer Schuetze <r.sagita...@gmx.de> --- My current idea is to abuse the "Code Definition Window" to show assembly instead. The assembly would be a file produced by compiling and dumping the file after saving it (or maybe after some new command invoked by a hotkey). The caret location inside the dump file would update according to a line number change in the editor. > Short of source, at very least, there needs to be symbol names at the header > of blocks of code. There are, but I'd like to avoid having to figure the actual mangled D symbol from the source (though feasable). Using debug line numbers seems better for navigating larger functions. > Do the GNU tools make this easier? The objdump tools that come with GDC or LDC don't produce really helpful results (and don't work on OMF and MS-COFF). When compiling to assembly, GDC adds location information which could be used, LDC does not (I might be missing some command-line switch, though). DMD can't build to asm anyway, so dumping an object file will be necessary anyway. Maybe I can rip some code from cv2pdb, it can read line number information from executables with CV4 and DWARF debug information. I'll have to add CV8 support for Win64 though. --
