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

Fix custom heap #1745

Merged
merged 3 commits into from
Jul 6, 2019
Merged

Fix custom heap #1745

merged 3 commits into from
Jul 6, 2019

Conversation

mikee47
Copy link
Contributor

@mikee47 mikee47 commented Jul 6, 2019

Should call umm_malloc, etc. not malloc().
Update to latest version of umm_malloc, and add support for poison checking.

@slaff slaff added this to the 3.9.0 milestone Jul 6, 2019
@slaff
Copy link
Contributor

slaff commented Jul 6, 2019

@mikee47 Did you try this PR on a real device?

@mikee47
Copy link
Contributor Author

mikee47 commented Jul 6, 2019

Yes, works on NodeMCU. I've never got the custom heap to work, until I found the reason today. It's odd, though, it must have worked at some point but can't find when that was; candidate for LTS I guess?

@slaff slaff merged commit e59da53 into SmingHub:develop Jul 6, 2019
@mikee47 mikee47 deleted the fix/custom_heap branch July 6, 2019 19:37
slaff pushed a commit to slaff/Sming that referenced this pull request Jul 7, 2019
* Fix custom heap

* Update umm_malloc to latest version

* Add support for poison checking
@slaff slaff removed the 0 - Backlog label Jul 7, 2019
slaff added a commit that referenced this pull request Jul 7, 2019
* Fix custom heap

* Update umm_malloc to latest version

* Add support for poison checking
slaff pushed a commit to slaff/Sming that referenced this pull request Jul 14, 2019
* Fix custom heap

* Update umm_malloc to latest version

* Add support for poison checking
@slaff slaff mentioned this pull request Sep 28, 2019
4 tasks
This was referenced Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants