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.
Only part of the debugging code has been completed. Other parts of remote development block QA so I've been focusing on them...
Partially working on Unix (no path mapping on Windows yet).
Debugging is (kinda) working. Please see #142505 for a fairly serious known issue.
after start debugging I receive GDB is not responding. I am used as server intel-solaris machines with gdb 6.6 and gdb 6.3.50
see comments above
I wasn't able to run debugging too: Configuration: Windows Vista -> Solaris 2.9, gdb 6.6 After starting debugging NB becomes frozen for a while and shows next error in dialog after: Cannot run program "start": Create Process error=2, The system cannot find the file specified
Please look in the gdb-cmds*.log file. If its only about 15-16 lines long and they all start with a number (after the initial ======== line) then this problem is the same as 142505 and not a separate problem). While I usually get a 2nd try to work, sometimes I don't.
yes, all logs beside first gdb run are the such as you talk about, but I run debugging more and more and have not get a resulat. I could not do step into for project independent how much I've run gdb before, so for me it is more serious then 142505.
*** Issue 142505 has been marked as a duplicate of this issue. ***
Fixed by updating JSch to version 0.1.39 in: http://hg.netbeans.org/main/rev/1d6297a76781, http://hg.netbeans.org/main/rev/4d17bdf066a2, http://hg.netbeans.org/main/rev/3ea5ca51a9ba
This fix does not work in case of client Linux and server intel-solaris with gdb 6.6.
Please provide symptoms. I just ran on Ubuntu (Hardy Heron) to Solaris 10 and debugging worked as expected. I ran with a private dev build with the latest changes (including ones which won't be in a nightly until tonight).
Please check if gdb actually started. The easiest way to do this is to go to /tmp and remove all gdb-cmds*.log files before starting a remote debug session. If the debugger starts, you should get a log file created (these files are sometimes removed when you exit netbeans, so check before that). Also, be sure you set a breakpoint or did a step-into when you started debugging. I've had many customers (and myself:-) think the debugger failed because they ran to completion and the debugger windows disappeared.
in last build I finally can do step into or run debugging, so closing bug as fixed.