MM Investigate use of static variables
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Locate MM_DumpInEventCmd and inspect how EventString is declared and used, including the surrounding memory-management behavior. Determine whether the static declaration is necessary to avoid stack usage; done means documenting the finding and, if appropriate, changing the declaration with relevant validation.
Written by the indexing model from the issue text.
Description
In MM_DumpInEventCmd, EventString is declared as static to keep it off the stack. Need to investigate whether this is necessary.
Imported from GSFCCFS-1562
- Dominant language
- C
- Stars
- 34
- Forks
- 33
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nasa/MM
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
enhancement
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
requirements
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
bug
Similar issues
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·
-
bug Self Built Image SNAPSHOT Supported Device target/ramips
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100