Skip to content

Fix bug #70951: Segmentation fault on invalid WSDL cache #18707

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

Closed
wants to merge 1 commit into from

Conversation

nielsdos
Copy link
Member

We mix in the endianness and the zend_long size to make sure cache files can't be used on incompatible architectures.

We mix in the endianness and the zend_long size to make sure cache files
can't be used on incompatible architectures.
Copy link
Member

@devnexen devnexen left a comment

Choose a reason for hiding this comment

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

just curious, why on master ?

@nielsdos
Copy link
Member Author

just curious, why on master ?

This changes the cache file names due to the checksum being different, effectively invalidating all WSDL caches.
Since this should be a rare occurrence anyway, master seemed safest (i.e. no surprises about caches being rebuilt for end users)

@nielsdos nielsdos closed this in 56abb31 May 29, 2025
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