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

MM: Provide and use symbol name in the Memory Manager dump file #88

Open
MichaelLambertson opened this issue Dec 21, 2022 · 0 comments
Open
Assignees
Milestone

Comments

@MichaelLambertson
Copy link

Describe the bug
Found in testing for PACE mission
The memory manager file header has space for the symbol name. This should be populated whenever a symbol is used for a memory dump - otherwise the source of the file data may not be understood. It is also needed if the file is to be used for loading data by symbol.
When the symbol name is present, the data has to be loaded using the address for the symbol plus the offset present in the load file.

To Reproduce

  1. Issue a MM dump-to-file command using a valid FSW symbol and a non-zero offset
  2. Downlink and examine the file. Verify the MM header contains the correct symbol, offset and appropriate data.
  3. If the items in (2) are present, issue a MM load file command and verify that the data is correctly reloaded to the specified memory location.

Expected behavior
No symbol name will be present in the MM header.

Code snips
The PACE FSW team has corrected this in their build 3.2.3 - so should be able to provide code.

System observed on:
PACE DLEON processor
OS: VxWorks 6.9
Versions
cFE 6.6.05
MM 2.4.1

Additional context
none

Reporter Info
Michael Lambertson Goddard Space Flight Center Code 582 / Vantage Systems, Inc.

@dzbaker dzbaker added this to the Equuleus milestone Jan 26, 2023
@dzbaker dzbaker removed the CCB:Ready label Jan 4, 2024
@jphickey jphickey transferred this issue from nasa/cFS Jan 4, 2024
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

4 participants