On Jan 15, 2009 11:16am, Nick Kew <[email protected]> wrote:
How do you propose to deal with configuration? Specifically, the interaction with enable-exception-hook, which means that a server built without it breaks the expectation that new modules can be added using apxs?
I may misunderstand your concern here. I think of --enable-exception-hook purely as whether the potentially-dangerous hook is available to any module. As mod_backtrace and mod_whatkilledus cannot perform a useful service without that hook, and the idea behind making the exception hook a configure option is that the user should think twice before enabling it, Apache configure should fail if backtrace or whatkilledus are enabled but the exception hook is not.
How do they interact with compiler optimisations? Should mod_backtrace detect optimised code and warn that the backtrace printed may be affected and misleading?
I think a warning in the documentation would be helpful to the naive. I don't think the code should be concerned with that consideration.
