temporary fix bug null pointer#5733
Merged
SteveMacenski merged 1 commit intoros-navigation:foxy-develfrom Dec 3, 2025
Merged
Conversation
Signed-off-by: suifengersan123 <yangabc810@gmail.com>
Contributor
Author
|
This bug is not only present in the foxy branch, but the logic related to this part in the main branch is the same as that in the foxy branch. If you have time, could you please take a look and let me know if this modification is acceptable? |
Contributor
|
@suifengersan123, all pull requests must be targeted towards the |
SteveMacenski
approved these changes
Dec 1, 2025
Member
|
@suifengersan123 open against |
8 tasks
Contributor
Author
Thank you for your reply, and I open the PR(#5749). |
This file contains hidden or 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
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.
Basic Info
Description of contribution in a few bullet points
I added null pointer checks in costmap_layer.cpp and layered_costmap.cpp respectively.
Description of documentation updates required from your changes
No user-facing documentation changes required (internal implementation fix)
No parameter changes or API modifications
Description of how this change was tested
AddressSanitizer validation: Compiled with -fsanitize=address and verified no SEGV errors occur
For Maintainers:
backport-*.