We have a project that builds and debugs fine on one PC, but when built on another one, the debugger won't launch. The IP address and connection are good, we can use Autoupdate to send the debug s19 file to the target, everything works except the debug launch. I have verified that there are no spaces in the file paths (as reported in other posts). The only difference we can find between the two machines is that one installed the Netburner SDK in c:\nburn and the other in c:\apps\nburn
When attempting to launch the debugger, only the Launching status indicator in the very lower right hand corner works for about 3 seconds, then it stops - nothing happens, no launch. The Console and Problem windows don't show any error messages, and the Program Netburner window and gas guage never appear.
Is there a log file somewhere we could read to find out what failed? Is there a way to launch the debuger from a DOS window so error messages can be read? Any way to diagnose the problem?
Debugger Doesn't Launch and No Error Indication
Re: Debugger Doesn't Launch and No Error Indication
As a quick test, how about installing to c:\nburn so they are identical, and seeing if it makes a difference? It would be a quick way to rule that one out.
Re: Debugger Doesn't Launch and No Error Indication
The question is not wheter continually starting over will make it work, because it usually does. What we would like to have is some generic troubleshooting tools for when the Eclipse visual integrated environment doesn't do something and no error goes to the standard output (console).
For this problem, our programmer deleted the whole project and re-imported all the files and then debug started working again - without re-installing the Netburner SDK and leaving it in C:\Apps\Nburn.
This is not the first time we have had to delete and re-create a project to get something to work, and it seems like there would be a better way. Each time you do this, you have to go back into the project build Properties, add custom include paths in the Directores for each build configuration, etc.
Are there no other troubleshooting tools? Handy tips like which system files might be deleted to force a default Debug launch? Should I be posting this on an Eclipse group instead of Netburner?
Thanks,
PH
For this problem, our programmer deleted the whole project and re-imported all the files and then debug started working again - without re-installing the Netburner SDK and leaving it in C:\Apps\Nburn.
This is not the first time we have had to delete and re-create a project to get something to work, and it seems like there would be a better way. Each time you do this, you have to go back into the project build Properties, add custom include paths in the Directores for each build configuration, etc.
Are there no other troubleshooting tools? Handy tips like which system files might be deleted to force a default Debug launch? Should I be posting this on an Eclipse group instead of Netburner?
Thanks,
PH