mod_backtrace and mod_whatkilledus to trunk?

[tr...@gmail.com]

These are in the 1.3.x branch but not trunk. From the number of hits on the  
web I'd guess that some folks have made tweaks to them but there's no  
obvious place to maintain those tweaks. (I've received a patch or two via  
e-mail before.)

Specific proposal: Take what is in 1.3 branch and port to trunk. This  
should be very close to http://people.apache.org/~trawick/mod_backtrace.c  
and http://people.apache.org/~trawick/mod_whatkilledus.c, but I'll try to  
ensure that any enhancements made in the 1.3 branch (eg, backtrace logic  
for additional platforms) are kept and I'll definitely ensure that any  
enhancements in the 2.x version which could possibly have come from folks  
other than myself or the code in the 1.3.x branch are omitted. Any such  
enhancements from other parties can be proposed later as with any other  
patch to httpd (and I'll prompt any folks I can find in old e-mails).

Note: I haven't yet checked that there are additional fixes in 1.3.x branch  
or in my copies of the versions for 2.x listed above, so this could be a  
purely theoretical issue.

Re: mod_backtrace and mod_whatkilledus to trunk?

[Eric Covener <co...@gmail.com>]

On Thu, Jan 15, 2009 at 9:31 AM,  <tr...@gmail.com> wrote:
> These are in the 1.3.x branch but not trunk. From the number of hits on the
> web I'd guess that some folks have made tweaks to them but there's no
> obvious place to maintain those tweaks. (I've received a patch or two via
> e-mail before.)

+1

-- 
Eric Covener
covener@gmail.com

Re: mod_backtrace and mod_whatkilledus to trunk?

[Nick Kew <ni...@webthing.com>]

trawick@gmail.com wrote:

> Specific proposal: Take what is in 1.3 branch and port to trunk. This 
> should be very close to 
> http://people.apache.org/~trawick/mod_backtrace.c and 
> http://people.apache.org/~trawick/mod_whatkilledus.c

+1 in principle

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?

How do they interact with compiler optimisations?  Should
mod_backtrace detect optimised code and warn that the
backtrace printed may be affected and misleading?

-- 
Nick Kew