VisualD Can now execute class/struct methods __debugOverview, __debugExpaanded, __debugTextView to customize display in the debugger
r.sagitario at gmx.de
Mon Jul 6 17:58:02 UTC 2020
On 05/07/2020 22:25, FunkyD wrote:
> On Sunday, 5 July 2020 at 18:58:50 UTC, Rainer Schuetze wrote:
I could not reproduce crashes with your code.
> Also, in the general options it has debug[Overview|Expanded|Visualizer].
> The help seems inconsistent with the various _debug functions.
The __debugVisualizer was an intermediate version of the name, I'll fix
> There seems to be a bug somewhere.
> I started a different project and copied that code and it works! I
> originally had it in another project. The new project has Visual Studio
> x86 mixed mode set for the debugger! I thought I read that it must be mago.
> So it seems to work but there seems to be a bug that causes a crash and
> does not properly handle.
> Ok, I changed the old project back from mago to VSx86MM and it works. So
> this seems to be an issue with mago.
The mago debug *engine* is considered legacy for Visual Studio versions
that don't have a recent "Concord" debugger, i.e. 2013 or earlier. Most
of its code is shared with the mago debugger *extension*, though, but
only the latter supports function execution.
> mago debugger
> can now evaluate class/struct methods/fields __debugOverview,
> __debugExpanded, __debugTextView to customize display in the debugger
> experimental: can now display ranges similar to arrays
> some performance improvements by caching some data while the
> debuggee is stopped
> I assumed mago debugger meant for mago debugger. In any case, the crash
> is not good(happens when I go from locals to watch).
Might be that some of the new functionality is not properly disabled
with the debug engine.
More information about the Digitalmars-d-debugger