Open
Conversation
Commit 6ed4ea6 renamed the function `mm_initialize` to `mm_initialize_heap`. This caused the pynuttx modules (e.g. `mm dump`) to be missing.
linguini1
approved these changes
Feb 15, 2026
XuNeo
approved these changes
Feb 15, 2026
Contributor
|
@sumpfralle please fix |
acassis
approved these changes
Feb 18, 2026
fdcavalcanti
approved these changes
Feb 18, 2026
Contributor
fdcavalcanti
left a comment
There was a problem hiding this comment.
Fix CI issue please. LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Commit 6ed4ea6 renamed the function
mm_initializetomm_initialize_heap.But the corresponding symbol name in pynuttx was not updated.
The memory-related pynuttx functions (e.g.
mm dump) do not work anymore since then.Impact
The python-based support for gdb debugging now supports the memory-related features again.
Testing
Previously the following stack trace was emitted when starting gdb with the pynuttx extension:
(a similar stack trace was repeated multiple times for various commands)
Now there is no stacktrace anymore. The gdb command
mm dumpworks again.