April 25, 2021 at 05:33 #30401
I tried to watch std::unordered_map on visualGDB and I can see only hashtable members without any pretty printing for that.
do you have any quick solution? (any natvis file that I can use to fix that?)
int main(int argc, char *argv)
std::unordered_map<int32_t, std::string> tmp;
tmp = “str0”;
tmp = “str1”;
thanksApril 25, 2021 at 08:25 #30402
Sorry, we don’t have a ready-to-use visualizer of unordered_map yet. It is on the roadmap, however it’s hard to give any time estimates now. As a workaround, please consider creating one manually as shown in this tutorial.April 25, 2021 at 09:55 #30405
Once you have any solution for that It will be great to get it even a temporary/walkaround solution (like a working visualizer that just need to plug and play)August 24, 2021 at 12:06 #31195
any updates with ready-to-use visualizer of unordered_map/set?
thanksAugust 24, 2021 at 12:22 #31196
We generally prioritize feature requests based on the number of affected users. As this is a very specific request affecting a very small number of users, and can be achieved by implementing a custom visualizer, it has a very low priority and will likely not be added anytime soon.
If your company holds multiple VisualGDB licenses, please let us know the email associated with your key, and we will assign a higher priority to this.October 14, 2021 at 04:43 #31533
first of all it’s not a weird question, it’s a STD container that VisualGDB cannot show. I don’t know about other users, but I guess I’m not the only one who need that, I just the first one to report about that.
second, I don’t know how to read the this container and how to write a custom visualizer for it. if it simple you’re welcome to share it, if it’s not so simple it doesn’t make any sense to ask users to do it.
About the company I worked on, I don’t know which one uses VisualGDB, and even I knew it’s not something I can share here.
I guess I will need to wait for Visual-Studio 2022 or other extension which will help me to build/debug a custom Linux/WSL2 and get rid of VisualGDB.October 14, 2021 at 08:28 #31534
Please note that VisualGDB focuses on improving the typical development scenarios that would otherwise take a lot of our customers’ time. E.g. we provide a powerful Clang-based IntellISense engine that allows exploring large code bases, more reliable debugger integration, convenient GUI for configuring common settings, deep integration with Valgrind, CMake and numerous other tools, etc. You can find more about VisualGDB features for Linux here.
If none of these features made VisualGDB worthwhile for you in 6 months, adding support for visualizing a very specific container will not make much of a difference. So instead, we have to focus on features that would make a difference in the context of common tasks (e.g. the newly added Code Explorer is a huge help when dealing with large projects).
You must be logged in to reply to this topic.