Join GitHub today
The following commit causes mod_perl (svn trunk) to fail on startup (on Windows, at least) using 5.21.8:
It works fine on the same system (VC++ 2010, with httpd-2.4.10) using 5.21.7.
I get an access violation in modperl_env_init() when trying to replace the now const PL_vtbls with its own versions:
/* replace with our versions */
Is this diddling with perl's globals an unreasonable thing for mod_perl to be trying to do? I fear the answer may be yes...
On Wed, Jan 28, 2015 at 2:30 AM, Steve Hay <email@example.com>
Yes, I think overwriting the vtables is unreasonable. What I think is more
Leon Timmermans wrote:
All of that plus.
Perl mg vtable ptrs are basically GUIDs. Even if all members in the
Further commenting, since MS is closed source and has1 developer, Win32