Skip to content
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

mission: fix potential segfault #1189

Merged
merged 1 commit into from
Sep 17, 2020
Merged

mission: fix potential segfault #1189

merged 1 commit into from
Sep 17, 2020

Conversation

julianoes
Copy link
Collaborator

I have seen a segfault happen in current_mission_item() and this is the only thing that potentially could have caused it, I think.

I have seen a segfault happen in current_mission_item() and this is the
only thing that potentially could have caused it, I think.
@julianoes julianoes added the bug label Sep 17, 2020
@julianoes julianoes merged commit 0984934 into develop Sep 17, 2020
@julianoes julianoes deleted the pr-fix-segfault branch September 17, 2020 07:24
@jtroeth1
Copy link

Hello,
Not sure if related...

I am seeing a segfault which has to be in these three lines:

System& uav = mavlink.system();
auto telemetry = std::make_shared(uav);
auto action = std::make_shared(uav);

It has to be in these lines because i have no other mavlink lines in my code. I'm not sure whats going on in the background to cause this.
Any help appreciated.

Thanks,

@JonasVautherin
Copy link
Collaborator

I think this is unrelated. Can you open a new issue with that, and specify which version of MAVSDK you are using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants