-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Port GDB Guide from NAV2 to ros2_documenation #4178
Comments
@Ryanf55 i think this is useful for developers, IMO probably we can move the ROS 2 generic part from Nav2 to ROS 2 doc? So that Nav2 just has a link to that? (Nav2 specific guide can stay in Nav2 repo.) |
Yes, that is what I had in mind. |
Can we tag this as " good first issue" and hopefully someone new gets inspired to do the work? |
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/growing-issue-with-ros-documentation/36075/65 |
hii, can I work on this issue ? |
Go for it! |
@GauravKumar9920 thank you very much, i will be happy to review. |
Shall, I commit the Tutorial first, followed by the improvements in the future commits.
p.s - some general examples have already been included in the documentation. |
Further, under what hierarchy of the ROS2 documentation shall I add this section in ? |
Yep, that sounds like a good plan. For which package, it does not matter. It might actually be a good idea to create a ROS package that intentionally has a segfault, so others can reproduce it. As far as where, I might put it under intermediate: |
Looks like there's other resources from Autoware explaining similar things. |
Closed by #4190 |
Purpose
NAV2 has an excellent guide on using GDB with ROS 2:
https://navigation.ros.org/tutorials/docs/get_backtrace.html
The guide has very little to do with NAV2, and is helpful for anyone using ROS.
This ticket is to keep track of porting the information over.
Improvements
--mixin debug
when compiling rather than modifying the CMakeLists to add debug symbols.Many IDEs will have some kind of debugger or profiler built in, but with ROS, there are few IDEs to choose.
is not as true with open source editors such as VSCode and most debugging is done on dev machines anywaysThe text was updated successfully, but these errors were encountered: