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

CFE_EVS_GenerateEventTelemetry should check return code from CFE_SB_SendMsg() #599

Closed
CDKnightNASA opened this issue Apr 9, 2020 · 3 comments

Comments

@CDKnightNASA
Copy link
Contributor

Is your feature request related to a problem? Please describe.
EVS, when called to send events, eventually calls down to CFE_EVS_GenerateEventTelemetry() which sends the event to the ports and to the SB via CFE_SB_SendMsg(). However, it currently does not check the return code from SendMsg().

Describe the solution you'd like
GenerateEventTelemetry() should report an error to SysLog (and the ports?) if it's unable to send the event to the SB (preferably including the original event inside the SysLog error report.)

Describe alternatives you've considered
Leaving it as it is, it's unlikely that CFE_SB_SendMsg() would generate an error.

Additional context
Note also that if SendMsg() [really SendMsgFull()] generated an error, it would send an event through EVS, causing a loop between SB code and EVS code (that will likely go on until the system crashes). Again, this condition is unlikely, but this logic should be fixed to prevent loops.

Requester Info
Christopher.D.Knight@nasa.gov

@jphickey
Copy link
Contributor

jphickey commented Apr 9, 2020

Haven't looked at this particular case, but I think there is some sort of loop prevention logic in play here to prevent this sort of thing.

@CDKnightNASA
Copy link
Contributor Author

I ...suppose... this lock will block on the second time through the loop:

CFE_SB_LockSharedData(__func__,__LINE__);

@skliper
Copy link
Contributor

skliper commented Sep 24, 2021

Duplicate of #1952

@skliper skliper marked this as a duplicate of #1952 Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants