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

[Bug] RoveComm MRDTSink SegFault (URGENT) #343

Open
ClayJay3 opened this issue Oct 26, 2024 · 0 comments
Open

[Bug] RoveComm MRDTSink SegFault (URGENT) #343

ClayJay3 opened this issue Oct 26, 2024 · 0 comments
Assignees
Labels
3-Star Indicates a moderate level of difficulty, requiring a good understanding of the topic or task. bug Unexpected behaviors or issues that cause the software to malfunction or produce incorrect results. logging Tasks related to improving, fixing, or adding logging capabilities to the system. rovecomm Issues related to RoveComm, the communication protocol used within the project.

Comments

@ClayJay3
Copy link
Contributor

Description

I have been trying to reproduce and track down this segfault for a long time, and it finally happened while I was running in the debugger, so I was able to get a good stack trace. This bug seems to be an issue with the RoveComm logger setup in quill, something about the packet or the data given to the pack packet method causes a segfault on the memcpy function. See Screenshots Below:
Screenshot from 2024-10-26 10-57-43
Here is where the segfault occured.
Screenshot from 2024-10-26 10-57-28
Here you can see that is happened in the quill thread when using the custom sink.
Screenshot from 2024-10-26 10-57-17
Here's the values of the local variables for PackPacket.

I was not using or subscribing to the sink.

Steps to Reproduce

This issue is somewhat rare and difficult to catch, but nonetheless important since we definitely do not want this to happen during testing or a competition. I do not have a list of steps to reproduce, so hopefully the info I provided in this issue is enough to fix the problem. I recommend fixing as soon as possible.

Expected Behavior

No segfault :)

Actual Behavior

It segfault :(

Logs

No response

Environment

Jammy

Version

development

Additional Context

No response

@ClayJay3 ClayJay3 added bug Unexpected behaviors or issues that cause the software to malfunction or produce incorrect results. 3-Star Indicates a moderate level of difficulty, requiring a good understanding of the topic or task. rovecomm Issues related to RoveComm, the communication protocol used within the project. logging Tasks related to improving, fixing, or adding logging capabilities to the system. labels Oct 26, 2024
@Byrdman32 Byrdman32 moved this from Backlog to In Development in URC 2025 - Autonomy Nov 11, 2024
@Byrdman32 Byrdman32 moved this from Backlog to In Development in URC 2025 - Software Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3-Star Indicates a moderate level of difficulty, requiring a good understanding of the topic or task. bug Unexpected behaviors or issues that cause the software to malfunction or produce incorrect results. logging Tasks related to improving, fixing, or adding logging capabilities to the system. rovecomm Issues related to RoveComm, the communication protocol used within the project.
Projects
Status: In Development
Status: In Development
Development

No branches or pull requests

3 participants