Skip to content

Conversation

@orlitzky
Copy link
Contributor

In https://github.com/php/php-src/commits/eaee504c4d4f337df11b56c251aaeec032b1ea51 the session's save_path global was changed to a zend_string pointer, but there are a few direct char-pointer accesses in ext/session/mod_mm.c that slipped through the cracks. GCC-15 notices them and fails to build due to the incompatible pointer types. Three ZSTR_* wrappers are all that is needed.

Gentoo-Bug: https://bugs.gentoo.org/967862

@ndossche
Copy link
Member

I'm confused. eaee504 went into PHP 8.5 and above, but your PR targets PHP 8.3 ?

In eaee504 the session's save_path global was changed to a
zend_string pointer, but there are a few direct char-pointer accesses
in ext/session/mod_mm.c that slipped through the cracks. GCC-15
notices them and fails to build due to the incompatible pointer types.
Three ZSTR_* wrappers are all that is needed.

Gentoo-Bug: https://bugs.gentoo.org/967862
@orlitzky
Copy link
Contributor Author

FFS. Sorry for the chaos.

You're not confused, I wasn't paying enough attention. I thought I knew which commit introduced the change.... wrote the patch, based it on 8.3, then realized that it was some other commit that actually introduced the change. But I forgot to check that the other (real) commit was in 8.3.

Copy link
Member

@Girgias Girgias left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this, I thought we built all the different session modules but turns out we don't...

@NattyNarwhal
Copy link
Member

mm is on the way out next time we can get rid of it though, I thought?

@ndossche
Copy link
Member

mm is on the way out next time we can get rid of it though, I thought?

IIRC David was working on a replacement using a different library that provides essentially the same functionality.

Copy link
Member

@ndossche ndossche left a comment

Choose a reason for hiding this comment

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

Thanks

@ndossche ndossche closed this in 0eb6a4d Dec 23, 2025
@orlitzky
Copy link
Contributor Author

Thanks! In case anyone is wondering, I don't use this myself or know anyone who does. The developer who reported the bug runs a tinderbox, building random packages in random configurations to find problems before our end users do. It's better to have it working in the meantime but if it gets replaced or nuked, that's fine too.

@alexdowad
Copy link
Contributor

Thanks! In case anyone is wondering, I don't use this myself or know anyone who does. The developer who reported the bug runs a tinderbox, building random packages in random configurations to find problems before our end users do. It's better to have it working in the meantime but if it gets replaced or nuked, that's fine too.

That's awesome. I hope the person in question gets some props for their good work.

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.

5 participants