Skip to content

Find where your code is crashing

doinkythederp edited this page Mar 14, 2025 · 7 revisions

VEX V5 frameworks such as PROS, VEXcode, and vexide don't give specific line numbers or file names after a crash; instead, they provide a hexadecimal address number describing the buggy code's location in the robot's memory. You can use the Visual Studio Code extension Symbolizer for VEX V5 to turn this number into something more useful for humans, revealing the exact line where your code crashed.

Install the Visual Studio Code extension

Symbolizer for VEX V5 is available in the VS Code extension marketplace and can be installed alongside the PROS or VEX Robotics (VEXCode) extensions:

https://marketplace.visualstudio.com/items?itemName=vexide.symbolizer-for-vex-v5

Installing this extension will allow you to find the location where your code crashed.

Identify the address

The address numerically encodes where your code crashed and can be easily identified as the string of letters and numbers on the second line of the V5 brain's display during a crash. It usually begins with 38 or 78.

VEXcode and vexide PROS
A VEXcode program displaying a memory permission error A PROS program displaying a data abort exception

The address is 03800128.

The address is 3801bd4.

Find the buggy code

In Visual Studio Code, press Ctrl+Shift+P (Windows, Linux) or Command+Shift+P (macOS) to open the command selector. Then, select "Jump to Address" and enter the address displayed on the brain's screen. The editor will then move the cursor to the crash's location.

The "Jump to Address" command, which reveals the crash location in the editor

Clone this wiki locally