You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The segfault in issue #42 was caused by specifying a command MID with a message not defined as a command (and which thus had no queue defined for it). The ECI code blindly attempted to utilize the queue which didn't exist, causing the segfault.
During the course of resolving that issue it was determined that a check can be done here to confirm the that there's a queue allocated if the MID indicates the message is a command.
That check would look something like if MsgRcv[idx].MsgStruct->qptr == NULL, issue an error event message warning the user about a misconfiguration, and either
skip the configuration of the queue for that message (if we can establish that the app will still work without it)
exit the app, if its going to be too broken to function
Work needs to be done to determine the correct course of action and implement this check.
The text was updated successfully, but these errors were encountered:
The segfault in issue #42 was caused by specifying a command MID with a message not defined as a command (and which thus had no queue defined for it). The ECI code blindly attempted to utilize the queue which didn't exist, causing the segfault.
During the course of resolving that issue it was determined that a check can be done here to confirm the that there's a queue allocated if the MID indicates the message is a command.
That check would look something like if
MsgRcv[idx].MsgStruct->qptr == NULL
, issue an error event message warning the user about a misconfiguration, and eitherWork needs to be done to determine the correct course of action and implement this check.
The text was updated successfully, but these errors were encountered: