Bugzilla – Full Text Bug Listing
| Summary: | Debug - Variables view - HashMap content, seeming keys collision | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Alessandro Leonardi <alessandro1leonardi> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | trivial | ||
| Priority: | P3 | CC: | Michael_Rennie, pwebster |
| Version: | 3.7 | Keywords: | needinfo |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
(In reply to comment #0) > Build Identifier: M20100909-0800 > > Trying debugging a simple code as reported below, the variables view will shown > a keys collision ( request and requestHeader ), but is only an apperent > collision, all keys are correctly displayed > Not sure I understand what you mean here. If I debug the snippet, I see a map with three keys and the following output in the console: request Request RequestHeader What do you mean by "an apparent collision"? Closing invalid |
Build Identifier: M20100909-0800 Trying debugging a simple code as reported below, the variables view will shown a keys collision ( request and requestHeader ), but is only an apperent collision, all keys are correctly displayed import java.util.HashMap; class HashTest { static public void main(String args[]) { HashMap myhm1 = new HashMap(); myhm1.put("request",new String("request")); myhm1.put("Request",new String("Request")); myhm1.put("RequestHeader",new String("RequestHeader")); System.out.println(myhm1.get("request")); System.out.println(myhm1.get("Request")); System.out.println(myhm1.get("RequestHeader")); return; } } Reproducible: Always Steps to Reproduce: 1. produce a main class as describe abowe 2. debug it