Document LD_LIBRARY_PATH and catching exceptions with GDB when testing #4175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ryan Friedman <[email protected]>
Signed-off-by: Ryan Friedman <[email protected]>
Signed-off-by: Ryan Friedman <[email protected]>
clalancette
approved these changes
Feb 16, 2024
There was a problem hiding this comment.
Given my comment below, I'm fine with this as-is. But I'd like to get @fujitatomoya to approve before we merge.
fujitatomoya
approved these changes
Feb 16, 2024
|
Can we get a backport to |
|
@Mergifyio backport iron humble |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Feb 20, 2024
#4175) * Document LD_LIBRARY_PATH and catching exceptions Signed-off-by: Ryan Friedman <[email protected]> * Uniform capitization of gdb Signed-off-by: Ryan Friedman <[email protected]> * Remove extra line Signed-off-by: Ryan Friedman <[email protected]> --------- Signed-off-by: Ryan Friedman <[email protected]> (cherry picked from commit d084dd8)
mergify bot
pushed a commit
that referenced
this pull request
Feb 20, 2024
#4175) * Document LD_LIBRARY_PATH and catching exceptions Signed-off-by: Ryan Friedman <[email protected]> * Uniform capitization of gdb Signed-off-by: Ryan Friedman <[email protected]> * Remove extra line Signed-off-by: Ryan Friedman <[email protected]> --------- Signed-off-by: Ryan Friedman <[email protected]> (cherry picked from commit d084dd8)
clalancette
pushed a commit
that referenced
this pull request
Feb 20, 2024
#4175) (#4176) * Document LD_LIBRARY_PATH and catching exceptions Signed-off-by: Ryan Friedman <[email protected]> * Uniform capitization of gdb Signed-off-by: Ryan Friedman <[email protected]> * Remove extra line Signed-off-by: Ryan Friedman <[email protected]> --------- Signed-off-by: Ryan Friedman <[email protected]> (cherry picked from commit d084dd8) Co-authored-by: Ryan <[email protected]>
clalancette
pushed a commit
that referenced
this pull request
Feb 20, 2024
#4175) (#4177) * Document LD_LIBRARY_PATH and catching exceptions Signed-off-by: Ryan Friedman <[email protected]> * Uniform capitization of gdb Signed-off-by: Ryan Friedman <[email protected]> * Remove extra line Signed-off-by: Ryan Friedman <[email protected]> --------- Signed-off-by: Ryan Friedman <[email protected]> (cherry picked from commit d084dd8) Co-authored-by: Ryan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
I ran into another test failure that I couldn't track down. According to the guide I wrote earlier, debug symbols only get loaded on the test itself.
Now, users are recommended to source their workspace. With this, gdb is aware of the path to all the libraries and get debug symbols correctly. I presume this is through LD_LIBRARY_PATH, but I could be wrong.
Additionally, exceptions thrown in ROS libraries are caught by gtest, and if you want to have gdb find them first, the workflow is slightly different.
There may be better ways to do this, but the workflow works well for me.
Real world example
ANYbotics/grid_map#401 (comment)
Why is this necessary
Well, I have grid_map installed with binaries, and then develop locally in the workspace with debug. The installed binaries are in release mode, so gdb is actually running the wrong library and I'm testing the wrong code under GDB. Forgetting to source the environment means you might be debugging the wrong code! This explains why any modifications I did seemed to have no effect.
What about VSCode
VSCode is great, but can't run a script before starting a debug session. This means that the GDB configuration cannot run
source install/setup.bashand have the environment configured correctly. I have yet to find a way around this other than telling people to learn CLI GDB.https://stackoverflow.com/questions/43836861/how-to-run-a-command-in-visual-studio-code-with-launch-json
Related
#3899