ARMmbed / ARMmbed/mbed-drivers

Test heap and stack - warning - does not iterate

Open
#135 3 comments 0 reactions 0 assignees View on GitHub
mirrored
Dominant language
C++
Stars
39
Forks
41
PR merge metrics
No merged PRs in 30d

Description

The test is outdated, as it assumes the stack is above the heap (and smaller than heap).

frdm-k64f-gcc output:

```
{{timeout;10}}
{{host_test_name;default_auto}}
{{description;Heap & Stack}}
{{test_id;MBED_13}}
{{start}}
Initial stack/heap geometry:
stack pointer:V 0x1fffa047
heap pointer :^ 0x1fffacb0

stack pointer: 0x1fffa02f
heap pointer: 0x1fffadc0

[WARNING] The Stack/Heap collision was not detected

Allocated (0)Kb in (1) iterations

{{success}}
{{end}}
```

This test should be in ualloc, and should be corrected/improved.

Thanks for bringing this up to @akselsm

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the heap and stack test and inspect the ualloc area, starting with how the test measures stack and heap geometry. Compare its assumptions with the frdm-k64f-gcc output and determine what corrected behavior should be covered; done means the test no longer reports a false warning and iterates as intended.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
embedded-iot, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.