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

Fix #887, specify shell name in ShellOutputToFile #938

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

jphickey
Copy link
Contributor

Describe the contribution
Rather than using a default name, use a specific name so that it can be polled more safely.

Fixes #887

Testing performed
Build and run coverage tests
Also enable shell and run "shell-test" on MCP750

Expected behavior changes
No longer using a string pointer which may be invalid.

System(s) tested on
MCP750, vxworks 6.9

Additional context
Although this while loop seems to be working OK, the overall "shell-test" actually fails on the MCP750 because it looks like the shell does not have an "echo" function. This seems to be a separate issue, not sure if/how this test ever worked.

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

Rather than using a default name, use a specific name so that
it can be polled more safely.
@jphickey jphickey added the CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) label Mar 31, 2021
@jphickey
Copy link
Contributor Author

Submitted issue #939 about related shell issue discovered when attempting to test this.

@jphickey
Copy link
Contributor Author

jphickey commented Mar 31, 2021

Also worth noting - this assumes that VxWorks will honor and use the shell name specified.

Technically the VxWorks documentation for shellGenericInit() says that the actual shell name may be different than the passed in shell name. But it appears that is only possible if using a single shared shell task, which is not the case on the MCP750 - and if that were the case then the original code would be broken too - because the shell task remains running after the command finishes.

@astrogeco
Copy link
Contributor

CCB 2021-03-31 APPROVED

@astrogeco astrogeco changed the base branch from main to integration-candidate April 8, 2021 02:39
@astrogeco astrogeco added CCB:Approved Indicates code review and approval by community CCB IC:2021-04-06 and removed CCB:Ready Pull request is ready for discussion at the Configuration Control Board (CCB) labels Apr 8, 2021
@astrogeco astrogeco merged commit 7746955 into nasa:integration-candidate Apr 8, 2021
astrogeco added a commit to nasa/cFS that referenced this pull request Apr 8, 2021
nasa/osal#931 - Scrub include guards

nasa/osal#937 - Switch to use CLOCK_REALTIME

nasa/osal#938 - Specify shell name in ShellOutputToFile
astrogeco added a commit to nasa/cFS that referenced this pull request Apr 8, 2021
Combines:

nasa/cFE#1284
nasa/osal#951
nasa/PSP#289

Including:

nasa/cFE#1251 - ES Info API Functional test

nasa/osal#931 - Scrub include guards
nasa/osal#937 - Switch to use CLOCK_REALTIME
nasa/osal#938 - specify shell name in ShellOutputToFile

nasa/PSP#286 - use OSAL timebase for CFE timers
nasa/PSP#282 - modularize the ram, port, and eenasa/psp#om access
nasa/PSP#285 - add psp module to implement timebase
@jphickey jphickey deleted the fix-887-shelloutput branch April 28, 2021 18:58
@skliper skliper added this to the 6.0.0 milestone Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCB:Approved Indicates code review and approval by community CCB
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OS_ShellOutputToFile_Impl in VxWorks is not thread safe
3 participants