Valgrind: Conditional jump or move depends on uninitialised value(s)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
==28010== Conditional jump or move depends on uninitialised value(s)
==28010== at 0x188900: createDir_IfDoesNotExist(std::__cxx11::basic_string, std::allocator > const&) (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x168B3E: SuperChunk::initialize() (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x14C9DB: main_function() (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x14E7D5: main (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== Uninitialised value was created by a stack allocation
==28010== at 0x188866: isDir(std::__cxx11::basic_string, std::allocator > const&) (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== Conditional jump or move depends on uninitialised value(s)
==28010== at 0x155A02: bool glm::operator==(glm::vec<3, float, (glm::qualifier)0> const&, glm::vec<3, float, (glm::qualifier)0> const&) (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x154AA4: bool glm::operator!=(glm::vec<3, float, (glm::qualifier)0> const&, glm::vec<3, float, (glm::qualifier)0> const&) (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x150F11: LocalPlayer::update() (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x150BED: LocalPlayer::LocalPlayer() (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x14C9EA: main_function() (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== by 0x14E7D5: main (in /home/baum/fun/BlockGame/build/mainLinux)
==28010== Uninitialised value was created by a stack allocation
==28010== at 0x14C0EB: main_function() (in /home/baum/fun/BlockGame/build/mainLinux)
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
Start by reproducing the report under Valgrind and trace the first stack through main_function(), SuperChunk::initialize(), createDir_IfDoesNotExist(), and isDir(). Then inspect the second stack through main_function(), LocalPlayer::LocalPlayer(), and LocalPlayer::update(), including the reported stack allocations. Done means Valgrind no longer reports these uninitialised-value conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100