Display `std::vector<int>` and other PoD types in watch window's elements?

[sonictk]

Hi, this is a bit of a feature request and might be out of scope for what RemedyBG focuses on, but I searched the existing issues and didn't see anything so I thought I'd ask: would it be possible to add support to view things like std::vector<int> and other basic PoD template specializations (float, bool etc.) in the Watch window to show the individual array elements (and if possible, for other things like std::map, std::unordered_map etc.)? I know most of the time people using RemedyBG probably don't use the STL for high-performance scenarios but it sometimes does prove useful when I'm doing small test cases or just coding exercises and want to use RemedyBG for debugging. :) In these cases I find myself going back to WinDbg just because it's able to handle display of these STL types with more convenience.

(Feel free to close this request if it's out of scope)

[Manuzor]

113 may be related. Basically a replacement for VS's natvis that provides views for std:: types would solve this.

[jcalabro]

Wanted to chime in and say that this would be super helpful for me! In particular, I'm often debugging other people's code that use i.e. std::vector, and I always need to go back to VS when that code relies on std very heavily.

[Chinayang1]

I have the same problem on the compony project that using STL heavily. Hope support easily watching STL variable.

[tv48341]

also would love a solution. I teach programming in high school and we rely on <vector> to create dynamic arrays so it would be great to clear up some of the abstraction and show students how a vector works 'behind the scenes'. Note I cant use VS debugger as it is way too slow on our budget school computers. Notice my terrible attempt at displaying a vector

[chrisbriend]

Would absolutely love to have natvis support ! Other than the standard library, any kind of large external library (Unreal/Havok/etc) may already provide it for hundreds of types. Being in the dark when using those types means having to fall back onto the msvc debugger. I also assume that within any company with a large enough codebase, someone will already have written useful natvis files for internal types... Those however could be converted to any other visualization format that RemedyBG prefers (as mentioned in #113 ) if the adoption rate is big enough

[nluka]

Would love to see this supported. This is the main thing which stops me from using remedy. Very difficult to make sense of STL containers in the watch window...

[yoacompsci]

Hi!! it would be great to have the std:: containers contents in the watch window with format.