This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
JavaRebel is a javaagent that lets developer skip application redeploys/restarts. When using NetBeans it is not possible to set breakpoint to JavaRebel enabled applications. Once an application has been started with JavaRebel, debugging session started in NetBeans and user tries to set a breakpoint the following message is displayed "Not able to submit breakpoint LineBreakpoint YourJavaClass.java : XX, reason: No executable location available at line 33 in class YourJavaClass.". I've attached a small patch that fixes the issue. This patch makes LineBreakPointImpl also check the ReferenceType's nested types. This enables users to set a breakpoint in JavaRebel enabled applications when debugging with NetBeans. As far as my tests and logic go this won't affect non-rebel applications. Correct me if I'm wrong.
Created attachment 63950 [details] Proposed patch
can we please have this evaluated applies in 6.7 timeframe? with javarebel 2.0 having support for maven projects, we can expect users to make use of javarebel more frequently. Thanks.
I think this is already outdated as our binary releases of the nb debugger jars have not been working with later versions of NB but I think the ideas behind the patch apply. See also http://www.netbeans.org/issues/show_bug.cgi?id=139045
Well, can you please explain first why this patch is needed? Is JavaRebel creating some nested classes from the original ones? If yes, when does it create them and how are they used? A similar code was already there, but now we work with the correct ReferenceType in ordinary Java debugging, therefore we do not inspect nested types any more. We want to notify users about broken breakpoints if they are not found in the given class and line number. This additional searches could cause submission of breakpoints where there should not be instead of marking them as broken.
I'm not up to date with the details of the patch any more, we'll assign a guy to debug the debugger and give you the necessary answers. As for broken breakpoints, there will be broken breakpoints added but the usual case is that at least one will succeed. If none succeed then it can be reported to the user. A bit offtopic, where is the best place to ask for help building Netbeans because I remember I had 30min build cycles because I was not able to build the debugging modules separately and had to build the whole IDE all the time.
@toomasr: IMHO this issue is obsolete!? I read a slide from zt months ago, that is was fixed in 7.2?