Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 384697

Summary: conditional breakpoint - [varname] cannot be resolved
Product: [Eclipse Project] JDT Reporter: Heiko Böttger <heiko.boettger>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: Michael_Rennie
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Heiko Böttger CLA 2012-07-10 04:46:18 EDT
Build Identifier: 20120216-1857

When setting a conditional breakpoint in URLClassLoader#findClass checking the name-parameter to contain as string: 

name.contains("List")

The debugger stopps with "name cannot be resolved" looking at the available variable shows that they are not known by their realname. The names are "arg0", "arg1", etc. Using "arg0" instead of "name" works. However when the evaluation error ("name cannot be resolved") occurs the location of the breakpoint is correctly shown in the source code, meaning the source code is available.


Reproducible: Always

Steps to Reproduce:
1. Setup a break point in URLClassLoader#findClass 
2. Setup the condition to stop at: name.contains("List")
3. Run a problem using a class named "List"
Comment 1 Michael Rennie CLA 2012-07-10 10:11:03 EDT
The reason we cannot compute the condition using the source var names is because there are no debug attributes available - the reason you see arg0, arg1, etc rather than names.

*** This bug has been marked as a duplicate of bug 33733 ***