-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode debug instructions #291
base: master
Are you sure you want to change the base?
Conversation
"type": "cppdbg", | ||
"miDebuggerServerAddress": "localhost:3000", | ||
"cwd": "/", | ||
"program": "$path_to_build_executable" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace with /path/to/build/executable
to make clear this should be replaced. As well below anywhere you use the $
syntax, I don't want people confused that it literally means that string.
] | ||
} | ||
|
||
The path to the build executable will be printed out when running gdbserver. You can also find it using ``ros2 pkg prefix $package_name``. This gives you the prefix. Add ``/lib/$package_name/$node_name`` to the prefix path to have the absolute path of the build executable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont understand the /lib
bit, where did that come from?
|
||
The path to the build executable will be printed out when running gdbserver. You can also find it using ``ros2 pkg prefix $package_name``. This gives you the prefix. Add ``/lib/$package_name/$node_name`` to the prefix path to have the absolute path of the build executable. | ||
|
||
You should be all set to debug with VSCode: run the GDB server, then use the ``Run and Debug`` panel to attach and start debugging your application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To do what? how? what does it look like? how do you interact with it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this talk to breakpoints in the editor, what can you do? Does the server need to be restarted adding traces?
There are alot of unanswered questions about how to use this or what you can do with this (and how)
|
||
.. code-block:: bash | ||
|
||
ros2 run --prefix 'gdbserver localhost:3000' <pkg> <node> --all-other-launch arguments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove --all-other-launch arguments
, that is implied
Co-authored-by: Steve Macenski <[email protected]>
Any update @guilyx ? I had a few problems that look acknowledged but not updated |
Hey, it's in my backlog, seen your feedback and will update when time allows me to 😬😬 |
OK! Just a friendly reminder :-) |
Just a quick ping again! |
PS but there's no Scriptum: Would be nice to have a
.gitignore
for_build