如果您确实指出了您正在使用的eclipse版本和技术(例如，Java JDT，或面向Java的AJDT，或c++ CDT)，这将有所帮助。

在Java方面，我猜想您的“勾选编译器选项中的复选框”指的就是这个

在“窗口—>首选项—> Java—>编译器—>类文件生成”下，所有“类文件”生成选项都设置为True:

(1)添加可变属性， (2) addline number， (3)添加源文件名， (4)保存未使用的局部变量。

您的项目是否只在全局级别(windows Preferences)或在项目特定级别检查这些?

你确定打开的类(你试图在上面设置断点):

是您的源代码之一(并且不是来自第三方库) 是。java，而不是。class?

尝试清理所有内容并重新构建所有内容，检查潜在的jar冲突。

我在一个特定的项目中遇到了同样的问题，我一直试图重置窗口中的行号属性->首选项…然后我意识到每个项目都有自己的行号属性设置。右键单击项目，进入属性，选择JavaCompiler，并选中“添加行号属性…”

因为我安装了6个不同版本的Java，所以我必须更改默认的JDK遵从性，以匹配我想使用的Java版本。当所有内容都使用Java 1.6构建/编译时，Eclipse默认将编译器遵从级别设置为Java 1.7。

所以我所做的就是

在eclipse菜单中，进入“窗口->首选项->Java->编译器” 在JDK遵从性下，我将编译器遵从性级别从1.7更改为1.6

现在Eclipse不再抱怨“无法插入缺少行号信息的断点”，并且调试断点实际上工作了!!

在调试部署到Tomcat的WAR(由多个Eclipse项目构件构造)时，我遇到了同样的问题。

我正在使用ANT构建脚本构建所有内容。如果这是您正在做的事情，请确保在您获得的每个javac ant任务上设置了debug=true标志。这是我唯一的问题-我希望它能帮助你的问题!

我在eclipse IDE中也遇到了同样的问题。我阅读了这个问题的所有答案，并尝试了几乎所有提到的设置，但运气不好。

所以，我尝试改变项目的运行时库，以前它是JRE - Java SE 1.8

我尝试将JRE更改为JDK，它为我工作:

从JRE切换到JDK的步骤如下:

Right click on project Click Properties -> Java Build Path Select tab - "Libraries" Click on "Add Library" button. "Add Library" window will open Select "JRE System Library" -> Click Next button Select "Alternate JRE" Click on Installed JRE button In New window click on "Add". This will open another window "Add JRE". Select "Standard VM". Click Next. Click on Directory button. Choose path of your "JDK" installation directory and click ok. Then Click Finish. Now check on newly added "JDK" Delete all other installed JRE's from the list(Optional) Apply-> OK Select "JDK from alternate JRE dropdown and Click on "Finish" Now from the list depicted below remove JRE instance Click Apply -> OK

你完蛋了!!

这里有详细的解释:

https://github.com/spring-projects/spring-ide/issues/78

只是为了将来参考，这是答案的相关部分(忽略引用Spring Boot应用程序的事实，在许多其他情况下行为是相同的):

Whenever you set a breakpoint in Eclipse/STS, the IDE tries to set the breakpoint in the VM if you launch an app. That is what happens in your case when you run the boot app in debug mode. For each class that gets loaded into the JVM, the IDE checks whether it needs to set a breakpoint or not. If it decides to set the breakpoint, the tries to do so (using the information from the breakpoint definition in the IDE, including its line number, since you usually set line breakpoints on a source file at a given line). This decision (whether to set the breakpoint on a given loaded class or not) checks the types that you set the breakpoint on, enclosing types, and inner classes. This makes sure that breakpoints for inner classes (even anonymous inner classes) are set to the JVM (and are not ignored). Spring Boot generates an inner class for your controller at runtime (this is the CGLIB generated inner class that appears in the error message). When the JVM loads that class, it tries to set the line number breakpoint of the enclosing type (for this inner class). Since the generated inner class doesn't have any line number information (it doesn't need to have line number information), setting the breakpoint fails for this inner class with the mentioned error message. When the IDE loads the enclosing type (your controller class itself), it also tries to set the line breakpoint and succeeds with that. This is visualized with the check marker on the breakpoint marker. Therefore you can safely ignore the error message that shows up. To avoid this error message to show up, you can go to the preferences (Java -> Debug) and disable "Warn when unable to install breakpoint due to missing line number attributes".