NetBurner Community Forum

I believe that the problem keckrl identified in the first post under this subject was fixed. There was an early beta release of 2.6 in which the debugger didn't work at all. If you look at this post and scroll down to the post by Forrest dated "Wed Aug 08, 2012 5:00 pm" you will see that the issues with the debugger that were addressed were: In this post, Tod and I commiserated over the issues we had with the debugger. I laid out my issues with the debugger in the latest release of 2.6.

I am guessing that my issues relate to the "timeout" fix not adequately addressing the long delays I have to deal with when debugging in the field. It would be difficult for support to replicate my problem, if it does relate to my field set-up.

On a fast PC running Windows 7, connected to the board by wire through a router, I don't have problems with the debugger, so not being able to replicate the problems in the "lab", I have hesitated to open a support ticket. Also, the device is working well now in the field and I haven't had to use the debugger out there lately.

Since there are not a lot of developers jumping in on this issue, either only two of us use the debugger, or no one else is having these issues.

Hope this helps you make your decision.

Ed

Just a comment on the "localhost:2159: No connection". The name "localhost" means "this computer" and is the loopback interface. You can open a command prompt and type "ping localhost" to do a loopback ping. It used to be that localhost would resolve to 127.0.0.1, but win 7 does IPv6 if you specify localhost so you see an address of ::1.

The message could be better, but its saying your debug connection target is your PC on port number 2159. You target needs to be the ip address of the netburner device, not the PC. Probably obvious to many here, just thought I would provide some background.