Search

Only 100 std::map elements in debugger by MKP-lwo

Active

5
0
Sign in
 to vote
Type: Bug
ID: 537218
Opened: 2/27/2010 8:04:11 AM
Access Restriction: Public
0
Workaround(s)
2
User(s) can reproduce this bug
There is a problem during debugging when I want to see all the elements of std::map container.

When debugger reaches the breakpoint and I want to check the values of the map in element inspector (in 'Locals' windows and in pop-up windows after hovering the variable name with mouse as well) and I'm scrolling down the list of the elements it stops on the 100 element and I can't next elements. The map contains more than 200 elements (map's counter parameter shows this properly) but I can't view them all in the element inspector.

The problem appears even in the most simple std::map<int, int> filled with 200 int values.

Used Visual C++ setting on first use and nothing changed after that.

edit:
I have attached the simplest project example that could ever be. I have also attached (inside *.zip file) exported settings in order to reproduce the situation in exactly the same environment settings.
Details (expand)

Product Language

English

Version

Visual Studio 2010 Release Candidate

Operating System

Windows 7

Operating System Language

English (UK)

Steps to Reproduce

Create std::map<int, int> container and fill it with anything with more than 100 unique keys. Then put a breakpoint just after the loop (or anything filling the continer) and try to debug the app.

Actual Results

There is only 100 elements of the container in Element inspector.

Expected Results

There should be all values of the container.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
File Name Submitted By Submitted On File Size  
mc.zip (restricted) MKP-lwo 3/1/2010 -
Sign in to post a comment.
Posted by Scot Br - MSFT on 4/14/2011 at 11:43 AM
Visual Studio 2010 Service Pack 1 introduced a fix for this issue in two ways:
1. The default limit was increased to 2000 instead of 100.
2. The default can be overridden by the use of a registry key (stand warnings about modifying the registry apply):
for x86: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\NativeDE\VisualizerMaxChildren
for x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\NativeDE\VisualizerMaxChildren

Scot Brennecke
Escalation Engineer, VC++ Support
Posted by Microsoft on 12/17/2010 at 11:44 AM
Hello Masterxilo and MKP-lwo,

Thanks for reporting this issue. I'm pleased to tell you that we were able to fix this issue and the fix is currently available as part of the VS 2010 SP1 Beta(http://www.microsoft.com/downloads/en/details.aspx?FamilyID=11ea69cb-cf12-4842-a3d7-b32a1e5642e2&displaylang=en)

Please try out that release and feel free to reactivate this issue if you don't believe the issue has been fixed.

Marc Paine
Visual Studio Debugger
Posted by masterxilo on 12/3/2010 at 6:00 AM
Duplicate of https://connect.microsoft.com/VisualStudio/feedback/details/608981/watch-window-does-not-list-all-elements-in-a-std-list-std-set-or-std-map-object-c
Posted by masterxilo on 11/13/2010 at 9:07 AM
The same limit applies to the std::list container...
Posted by Microsoft on 3/10/2010 at 6:12 PM
Thanks for taking the time to report this. This problem was introduced when fixing a different issue when inspecting containers with the debugger. Unfortunately when the other bug was fixed, a value of 100 was chosen as a limit for this. Obviously that limit is too low, unfortunately we will not be able to fix this before Visual Studio 2010 RTMs, but will look to fix it in the future.

Best Regards,
Visual Studio Debugger
Posted by MKP-lwo on 3/2/2010 at 1:08 PM
Requested sample project has been uploaded.
Posted by Microsoft on 2/28/2010 at 10:19 PM
Thanks for reporting this issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please give us a demo project to demonstrate this issue so that we can conduct further research.

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 3 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Visual Studio Product Team
Posted by Microsoft on 2/27/2010 at 7:06 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement