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.

Bug 241139 - Breakpoints not submitted to debugger
Summary: Breakpoints not submitted to debugger
Status: RESOLVED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.4
Hardware: Macintosh Mac OS X
: P2 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 22:41 UTC by dgrald
Modified: 2014-02-20 07:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dgrald 2014-01-29 22:41:18 UTC 
We have integration tests in a separate Maven module, and when we attempt to debug the integration tests, the breakpoints established within the tests or other modules are not submitted to the debugger. Thus, we are unable to stop at any of our established breakpoints. As a workaround, we're able to debug these tests in Netbeans via the Surefire plugin in the command line (http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html). Here are the options I'm using in my .conf file: netbeans_default_options="-J-client -J-Xss2m -J-Xmx4g -J-d64 -J-XX:PermSize=256m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true -J-Dsun.java2d.dpiaware=true -J-Dsun.zip.disableMemoryMapping=true"
Comment 1 Martin Entlicher 2014-02-11 21:40:52 UTC 
When the breakpoints are not submitted to the debugger, are there any messages in Debugger Console? We print messages there when breakpoints become invalid, etc.
Or please provide some sample project we can test...
Comment 2 dgrald 2014-02-20 00:12:04 UTC 
I'm sorry, the only output in the Debugger Console is:

Listening on 50246
User program running
User program finished


It doesn't output the established breakpoints like the following, which is output when debugging a unit test in another module:

LineBreakpoint COUNTRY_CODETest.java : 54 successfully submitted.

I'll try to assemble a sample project in order to try to reproduce.
Comment 3 Martin Entlicher 2014-02-20 07:31:34 UTC 
Thanks, with a sample project we will find the problem.