Can consistently reproduce the crash on a given, simple, native C++ code sample:
1. Put breakpoint in the first line of a member function.
2. When stopped, switch between "locals" and "auto" debug windows a couple of times.
3. Step over (F10) the next line
4. Repeat steps #2 and #3 until crash occurs (usually one iteration is enough).
This looks like just what I need to analyze some arrays (with the array plotter). However, I'm not doing any parallel programming. I can't choose anything else other than "Object Expander" from the drop down menu.
Is there any way to see if the viz pack installed correctly?
Is there any way I could get this to work in my case?
If you are seeing "Object Expander" in the drop down menu then it means the pack was installed correctly. The list of visualizers shown in the drop down menu depends on the type of the data you are trying to visualize.
The array plotter you mention is for arrays in native code and works in the regular watch window (not parallel watch). To see it in action, try viewing an int array in the watch window and you should be able to see visualizer icon next to it and launch array plotter.
Thanks for the reply. I was trying to use the array plotter for C#. Using this extension, I worked around the limitation by creating an artificial Parallel.For loop with a thread.sleep call inside. Ugly hack, I know, but in my specific case it kind of worked.
The extension works great, but so far I discovered a minor bug: the name of the array in the parallel watch window gets truncated from one VS session to another. For example: if I have a parallel watch on "projectedLight2[i]", the next time I open VS it will be truncated (and hence not found) to "projecte".