-
Notifications
You must be signed in to change notification settings - Fork 283
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
Fix JTC segfault on unload #515
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #515 +/- ##
==========================================
- Coverage 35.78% 32.48% -3.31%
==========================================
Files 189 7 -182
Lines 17570 665 -16905
Branches 11592 357 -11235
==========================================
- Hits 6287 216 -6071
+ Misses 994 157 -837
+ Partials 10289 292 -9997
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
The change makes total sense to me. I would however love to see a small test case, and the git messages could be squashed and the message could be a little bit more verbose.
Just my 2 cents.
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.
Great!
It would be cool to have small test case, but otherwise cool!
8e1757c
to
3b597d7
Compare
This commit fixes the segfault which happens when the JTC is unloaded, if it is in inactive state but was never activated.
3b597d7
to
60d3fa4
Compare
Done! Commits are squashed and I also added a small test case. |
@Mergifyio backport to humble |
This commit fixes the segfault which happens when the JTC is unloaded, if it is in inactive state but was never activated. (cherry picked from commit 6369faa)
✅ Backports have been created
|
Based on the discussion in #423 - the traj_home_point_ptr_ is a nullptr until the node is activated, so unloading from configured state (if no activation happened before) results in a segfault.