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

Bug 304498

Summary:	Content assist is broken for conditional breakpoints in classes without debug symbols
Product:	[Eclipse Project] JDT	Reporter:	Missing name <davidb.arbete+bugs+eclipse.org>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	Michael_Rennie, remy.suen
Version:	3.5.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Missing name

2010-03-03 06:57:52 EST

Build Identifier: 20090920-1017

Content assist suggestions are invalid for classes not compiled for debug (e.g., the standard classes in J2SE). For example, it suggests the actual variable names when only argN can be used.

See http://wiki.eclipse.org/FAQ_How_do_I_set_a_conditional_breakpoint%3F

I set the severity to major since the suggestions actually are false which misleads the user.

A preliminary fix to reduce the severity level would be to include a warning (with a hint about the workaround) when using content assist under these circumstances and/or disable content assist fully.

Furthermore, as far as I could see, the relevant online documentation is also erroneous and needs to be updated to reflect this problem.

Reproducible: Always

Comment 1 Remy Suen

2010-03-03 07:21:23 EST

Issues and concerns with the Java tooling's debug framework goes to JDT/Debug (Java Development Tools) and not Platform/IDE (which is for more generic IDE-related things like the 'Problems' view which applies to all programming languages and even non-programming related tasks).

Comment 2 Michael Rennie

2013-12-06 14:27:14 EST

It would be better to be able to detect that the classfile does not have debug infos and not even allow a breakpoint (or condition) to be set in it. That is covered by bug 329937.

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