Quote:
Originally Posted by Greg McKaskle
I see many C++ teams doing debugging using only print statements. But if you can get the debugging protocols running, you can have some pretty nice tools.
The basics -- breakpoints and pause/resume -- are present in both. The C++ equivalent to a probe is a watchpoint. C++ doesn't have panels that you can open, but you can use watchpoints or print statements. If you get fancy, you can instrument the code to place some important values to SmartDashboard.
Fancier tools such as profiler are not as commonly used, and I believe you have it in the WindRiver tools that come with FRC. Even fancier tools such as tracing are again available in both, but I'm not sure if FRC WindRiver contains it.
Greg McKaskle
|
Although your probably right that most C++ teams just use print statements, that is more of a problem with the teams than the language. If you take the little amount of time to time to learn how to do it, the smartdashboard can be easily used for debugging and displaying values. In fact, if you use robotbuilder, a lot of these debugging tools can be included in your code with just the click of a checkbox. The problem is that teams just don't usually realize its that easy, while with LabVIEW those tools are pretty hard to miss.