https://bz.apache.org/bugzilla/show_bug.cgi?id=57525
--- Comment #6 from Jose Kahan <[email protected]> --- I did some further tests under gdb. As the code shows, the macro module commands are marked as EXEC_ON_READ. This means that they are processed even before the preconfig hook is run. As a result, the definition of the macros only exists for the main configuration. @Yann patch deletes the macros right after, when the preconfig hook is run. @Terra's patch does the same, when the temp_pool is deleted. In both cases, the macro definition doesn't exist anymore when they are used in a .htaccess file. The error logs shows in this case. This is a regression compared to previous pre-patched behavior. The behavior that @Terra first reported is triggered because we're using a macro_section() is initialization ap_macros using cmd->temp_pool, which is used after being freed. If these macros need to be keep alive throughout in order to be used in .htaccess files, why the code is not using cmd->pool instead? Just for curiosity, I tried to do this change with @Terra's patch and the regression went away. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
