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

Diagnostics for developer mode #1009

Merged
merged 1 commit into from Aug 5, 2013
Merged

Diagnostics for developer mode #1009

merged 1 commit into from Aug 5, 2013

Conversation

ghost
Copy link

@ghost ghost commented Aug 5, 2013

This patch makes sure that the memory frame is restored by that very function which created it.

If a function tries to restore the frame it did not create, a warning is printed and backtrace is provided.

This ensures the proper frame nesting.

The patch also detects when a MM function/macro (like PHALCON_INIT_VAR()) is invoked without calling PHALCON_MM_GROW() first.

All checks are performed only when PHALCON_RELEASE macro is not defined and therefore the patch affects only developer builds.

phalcon pushed a commit that referenced this pull request Aug 5, 2013
Diagnostics for developer mode
@phalcon phalcon merged commit e7d066d into phalcon:1.3.0 Aug 5, 2013
@ghost ghost deleted the mm branch August 5, 2013 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants