Visual Studio Code, Code-D and Microsoft's Visual C++ Debugger (cppvsdbg)
Void-995
void995 at gmail.com
Wed Sep 19 14:45:39 UTC 2018
On Wednesday, 19 September 2018 at 14:37:32 UTC, Void-995 wrote:
> On Wednesday, 19 September 2018 at 14:29:27 UTC, Vladimir
> Panteleev wrote:
>> [...]
>
> Unfortunately you can't make Natvis to understand D symbols as
> it's purely for C++. You can make C# extension for Visual
> Studio to do pretty much whatever, but that's not usable much
> as it doesn't work for VS Code from what I found (and C# are
> extremely complex for this matter from my point of view). I
> think Visual D is using Mago internally via DLLs or something,
> and doing it's own thing.
>
> Something like -gc would be great to have again (I guess I
> missed that one), even -gcpp (to pretend it's C++) that can be
> used by pretty printing in GDB (fairly simple changes in Python
> scripts from printing standard C++ stuff) and Microsoft's
> Debugger. So the classes, namespaces, containers, dynamic
> arrays can be easily represented with actually having structure
> and sense from C++ point of view.
Forgot to mention that Microsoft added partial support (that may
be more than sufficient for D case) to their C/C++ in VS code for
both GDB and LLDB. So this one may be useful to make debugging
more friendly on Linux and Mac as well!
More information about the Digitalmars-d
mailing list