summaryrefslogtreecommitdiffstats
path: root/platform/javascript/audio_driver_javascript.cpp
diff options
context:
space:
mode:
authorMitten Orvan <Mitten.O@gmail.com>2024-05-04 19:32:55 +0300
committerRémi Verschelde <rverschelde@gmail.com>2024-05-11 12:33:35 +0200
commit829c33aed1022dc767460dbc2bec2f96ce06d0fa (patch)
tree76fd8439da97a30ff26a12769bb542163a411347 /platform/javascript/audio_driver_javascript.cpp
parent2ba22d1554ded08094e3869a83bd87487266ad38 (diff)
downloadredot-engine-829c33aed1022dc767460dbc2bec2f96ce06d0fa.tar.gz
Create a GDB pretty printing file for String, StringName, and Vector
GDB supports custom pretty-printers implemented in Python. When debugging Godot, checking the values of Strings and StringNames in the debugger was very inconvenient as the data is fairly deep in the structure. This makes the values immediately visible. The custom pretty printer can be taken into use manually by calling `source misc/scripts/godot_gdb_pretty_print.py` in the GDB console. In VS code, it can be activated by default by adding the source command to the `setupCommands` of the configuration in launch.json. Like this: ```json // launch.json { "configurations": [ { "name": "C/C++: debug, "type": "cppdbg", ... "MIMode": "gdb", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true }, { "description": "Load custom pretty-printers for Godot types.", "text": "source ${workspaceRoot}/misc/scripts/godot_gdb_pretty_print.py" } ], "miDebuggerPath": "gdb" } ], "version": "2.0.0" } ``` Extended the pretty-printer python script to support Vectors. The printer needs to be uncomfortably aware of CowData implementation details, but I don't think there is any way around that.
Diffstat (limited to 'platform/javascript/audio_driver_javascript.cpp')
0 files changed, 0 insertions, 0 deletions