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.
[dev-200503011900, JDK 1.5.0_02] If user invokes debug target on command line for project created in IDE she would get really scaring error message: -debug-start-debuggee: [java] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) [java] ERROR: transport error 202: connect failed: Cannot assign requested address ["transport.c",L41] [java] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L497] [java] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized [java] Java Result: 1 Similar message is printed on JDK 1.4. I think that's it's useless to try to start debugee process if no debugger is waiting.
Right symptoms, wrong diagnosis. The debug target is OK if you set -Djpda.address=..., but the current build-impl.xml does not check that it is set. Need a one-line addition: <target name="-init-macrodef-debug"> <macrodef name="debug" uri="http://www.netbeans.org/ns/j2se-project/1"> <attribute name="classname" default="${main.class}"/> <attribute name="classpath" default="${debug.classpath}"/> <attribute name="args" default="${application.args}"/> <sequential> <!-- HERE: --> <fail unless="jpda.address">Must set property 'jpda.address' to start program in debugger</fail> <java fork="true" classname="@{classname}" dir="${work.dir}" jvm="${platform.java}"> <!-- ... -->
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team