We have been know to crash the RoboRio with our C++ program. 🙂
Where would we find crash logs in order to determine why the program crashed?
We have been lucky enough to work backwards and remove code then figure out what the problem was. Accessing crash logs seem like it would speed up the process of working out where the bug is.
Is it the roboRIO that crashes or is it your program? When this crash occurs what does the status light on the roboRIO do? Also, what programming environment are you using?
Is it the roboRIO that crashes or is it your program?
It's our program (NULL pointers have been the common problem). Characteristically, we download code, reboot the program (not the entire RoboRIO), enable, then one of the driver station inidicators goes red (I'm not remembering which indicator, but it clearly indicates that our program has crashed.)
When this crash occurs what does the status light on the roboRIO do?
I haven't been looking at the RoboRIO. We've been looking at the drivers station.
Also, what programming environment are you using?
First make sure you are using the latest version of the WPILib Eclipse plugins. One of the updates contains a modification that makes sure that the log file is line buffered instead of 4k buffered.
Then, after running your program, look in /home/lvuser on the roboRIO for FRC_UserProgram.log. This is a symlink to the actual logfile in /var/local/natinst/log/