MetOffice / MetOffice/lfric_core
Evaluate Valgrind as part of our development process
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 26
- Forks
- 73
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
Valgrind is a widely used tool, actually, a suit of tools, for examining software memory usage and potential faults. It is commonly used to detect leeks and will also flag up potential issues such as writing to memory before it is allocated.
Although originally developed for C languages and still most powerful when used in that mode, it still offers much to the Fortran developer.
It might be integrated with our test suite but there may also be value in having it is part of our build system.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files, tests, or build entry points are named. Start by reviewing the existing test suite and build system to determine how Valgrind could be evaluated, then document a concrete integration approach and what successful memory-checking coverage would look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100