NetBeans Debugger not working this year?

[shindigo]

The past two years we have been able to use the debugger in NetBeans to step through our Java code running on the Robot.

This year, we cannot get it to work.

We set a breakpoint and run in debug mode. Windows Firewall comes up asking us to verify the access. We click 'Allow', but NetBeans cannot connect to the process on the robot.

The error is something like "Connection Refused" - in the debug console.

Could someone else give this a try and let me know if you can get it to work?

We're using NetBeans 7.2.1 with the 2013.0.417 FRC Plugins. I know we have a 2013 cRIO image - I think it is the latest.

thanks - sh

[Fauge7]

Yes, my team has the same problem, we got it working once, them ot stopped for no reason

[kylevedder]

For some reason, debugging only works when wired into the robot, not over wireless. Try plugging into the robot bridge with and ethernet cable.

[Joe Ross]

I could not get debugging to work during this year's beta test, and reported it. However, no one else complained about it, so I'm not sure if that means nobody debugs with netbeans, or that I was the only one with a problem.

[Chiller]

It was working for me when I was on my laptop (using wireless, ip was set to 10.xx.yy.12, subnet was 255.0.0.0)... So idk why its not working for you all?

[BradAMiller]

I just tested the current release using these steps:

http://wpilib.screenstepslive.com/s/...-robot-program

Be sure to set a breakpoint at the beginning of the program before you attach the debugger. You should see it stop at the breakpoint line and you'll have control to single-step or the other debugger operations.

Please post if it doesn't work.

Brad

[gixxy]

We have gotten ours working several times from both Windows and Linux boxes, however in all cases the computer had to be tethered.

[F22Rapture]

Originally Posted by Chiller

It was working for me when I was on my laptop (using wireless, ip was set to 10.xx.yy.12, subnet was 255.0.0.0)... So idk why its not working for you all?

Subnet needs to be 255.255.255.0 for it to work, otherwise you will have no communication with that computer.

[Joe Ross]

Multiple people on my team tried to get the debugger running wirelessly, with no success. I just tried it tethered and it worked.