Skip to content

signatures: don't leak an OP_NULL for a '$ =' sigscalarelem #23203

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

Merged
merged 3 commits into from
Apr 19, 2025

Conversation

tonycoz
Copy link
Contributor

@tonycoz tonycoz commented Apr 16, 2025

Fixes #23187


  • This set of changes does not require a perldelta entry.

@jkeenan
Copy link
Contributor

jkeenan commented Apr 16, 2025

Is there a regression test we could write for this?

@tonycoz
Copy link
Contributor Author

tonycoz commented Apr 16, 2025

Is there a regression test we could write for this?

It's already causing the part of the failures described in #23187.

Copy link
Contributor

@leonerd leonerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code change LGTM, though I think the comment could be worded slightly clearer for the benefit of future readers.

@mauke mauke force-pushed the 23187-signature-leak branch from c080708 to 507cff7 Compare April 19, 2025 15:36
@mauke mauke merged commit 6dc7328 into Perl:blead Apr 19, 2025
2 checks passed
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.

Memory leak for signature with unnamed parameter and empty default
4 participants