Hello,
I am getting a heap corruption on my team's robot and I would like to verify that my robot's image is valid. Can someone please compute and post the checksums of your copy of the 2014 image. The problem appeared when I reimaged the cRIO to 2014v52. While running the 2013 image the robot does not crash. When I instantiate a Gyro, WPILib silently corrupts memory. I can demonstrate this by running (
https://gist.github.com/electromatter/8995248) in test mode. When I run that program in Test mode and switch to Teleop, the robot crashes within a second. However, when I run the program only in Teleop, the robot does not crash. The jump to 0xEEEEEEEE is not consistent.
related files:
C:\WindRiver\WPILib\cRIO_Images\FRC_2014_v52.zip
C:\WindRiver\WPILib\WPILibC++Source20140101rev3876 .zip
C:\WindRiver\vxworks-6.3\target\lib\WPILib.a
md5 sums:
1077394c36cb21eb698ef16484c4c14c FRC_2014_v52.zip
a769926dbce97e3f9222e6fa79281068 WPILib.a
84869dd148975d43b8fad2670a6a02b8 WPILibC++Source20140101rev3876.zip
sha1 sums:
0989431bad7e34d5fcce2d42e290aa313dafb764 FRC_2014_v52.zip
a7edb741b589fb53f8e49eaaa38cd242de463dfa WPILib.a
bd6de27d6ba8c6814c2ba43f6e0f121bb8876ecc WPILibC++Source20140101rev3876.zip
Information from the debugger:
Exception in Kernel Task FRC_RobotTask:0xd0ce00
at pc=0xEEEEEEEC
Vector 0x200: Machine Check status=0xEEEEEEEE
Faulting module: FRC_RobotTask - 0xd0ce00
Stack trace:
0xEEEEEEEC
LiveWindow::SetEnabled() - LiveWindow.cpp:64
SimpleRobot::StartCompetition() - SimpleRobot.cpp:141
RobotBase::robotTask() - RobotBase.cpp:145
vxTaskEntry() - 0x000b48cc