Inspecting core dumps

[royerboat]

Hello,

We are having an issue with our robot periodically restarting. We SSH'd into the roboRio and set some options to generate a core file. When the frcUserProgram crashed, we saw a message saying "free(): invalid next size (fast): " and got a core file. We could not find GDB or other tools to read the core file on the roboRio. Is there another way to inspect the core file on or offboard the roboRio?

We did not see a stacktrace in the console or in the driver station logs. We also write our code in C++.

Thanks!

[PeterJohnson]

It isn't really easy to debug a core file. These instructions are a bit dated, but are what you need to run a cross-gdb on the desktop side to debug it. https://www.chiefdelphi.com/t/fatal-robot-code-crash/427074/34?u=peter_johnson (if this is a C++ program, it's a bit easier, but you still have to have all the debug shared libs available and set solib-search-path appropriately). An easier option is to use the debug robot code option in vscode, which will run debugging interactively (via a gdb remote connection).

[royerboat]

Thanks for the link with details. I'll try it out and let y'all know how it goes.

Unfortunately, this problem seems to not occur when using the debug robot code option in vscode. :(