Visual Studio natvis and incomplete types

I am writing a natvis file for a project in which some structures are defined "privately", that is, in .c code files, not headers.

When I debug a module where structs are defined, the debugger picks them up, but when working with pointers to those structs in other modules, I lose all the internal details and see instead {...}

. I can get around this by specifically hovering the object over the structure name specified in the module, for example. (MyModule.dll!MyStruct*)MyPointer

and that's ok for general development. But when writing the natvis files it got hurt.

I can create an item ExpandedItem

to display a properly selected object. But I really want to make a few items Item

that select key variables, and if I do, then I'm stuck with "Raw View" giving me only {...}

. Attempts to do both of these things at once lead to recursion. It's also very ugly to pour a lot this

in the natvis file.

Can I tell the debugger to recognize the complete type definition on its own?

+3
c visual-studio-2013 incomplete-type debuggervisualizer natvis


source to share


No one has answered this question yet

Check out similar questions:

566
How to disable all title headers in Visual Studio
402
Is there a format code shortcut for Visual Studio?
328
How can I switch my subscriber to Visual Studio 2013?
176
Unable to type Visual Studio
8
Custom natvis files in Visual Studio 2012
6
How does Visual Studio 2015 Natvis render a static variable function?
2
Visual Studio .natvis Samples File - Matrices
1
Visual Studio 2015 Natvis thinks QString is enum instead of type
0
Visual Studio natvis displaying an interface pointer
0
How can I refer to a variable directly from a natvis expression in C?



All Articles
Loading...
X
Show
Funny
Dev
Pics