确保运行时的主类所在的项目与包含断点的类所在的项目相同。如果不是，请确保两个项目都在运行配置的类路径中，并且出现在任何jar和类文件夹之前。

从Spring AOP得到这个消息(似乎来自CGLIB库)。点击忽略似乎工作正常，我仍然可以调试。

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

我也遇到了同样的问题，我花了很多时间去寻找解决方案，但这些解决方案都是无用的，所以我自学了所有的案例，最后我发现问题是JDK版本之间的冲突。 以下是解决问题的步骤: 1. 删除所有JDK和JRE版本，只保留一个版本。 2. 在Eclipse中设置JAVA_HOME系统和java编译器是一样的。 在某些情况下，上面的错误不会消失，但我们能够运行在调试模型。

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

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

这里有详细的解释:

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".