httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Trawick" <traw...@gmail.com>
Subject Re: mod_backtrace and mod_whatkilledus to trunk?
Date Thu, 15 Jan 2009 18:39:46 GMT
On Thu, Jan 15, 2009 at 12:40 PM, "Plüm, Rüdiger, VF-Group" <
ruediger.pluem@vodafone.com> wrote:

>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Nick Kew
> > Gesendet: Donnerstag, 15. Januar 2009 18:27
> > An: dev@httpd.apache.org
> > Betreff: Re: mod_backtrace and mod_whatkilledus to trunk?
> >
> > trawick@gmail.com wrote:
> > > On Jan 15, 2009 11:16am, Nick Kew <nick@webthing.com> 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.
> >
> > There's a general expectation that you can compile modules
> > using apxs, without having to recompile the core.  So long
> > as the fatal-exception hook is a compile-time option,
> > your modules break that expectation.
> >
> > If your modules go into trunk, that puts them on track for
> > future release versions where they'll be exposed to users
> > who can't be expected to recompile the core.
>
> OTOH if these modules are in trunk and you have a binary without
> this hook and thus without mod_backtrace and mod_whatkilledus
> who really tries to compile single modules from our distribution
> via apxs without compiling the whole thing?
>
> Another option would be to add this hook by default and prevent its
> execution by a directive (haven't dug into this to check if this is
> possible).


which reminds me: The 2.x hook is already protected both by a configure
option which defaults to no and a directive which defaults to Off ;)

See http://httpd.apache.org/docs/2.2/mod/mpm_common.html#enableexceptionhook

See some comments from Joe about why not to even allow the directive by
default at https://bugzilla.redhat.com/show_bug.cgi?id=205627

(I've worked with customers using these modules to help diagnose problems in
countless situations and don't remember where they were impediments, but I
guess I wouldn't ;)  That's not to say that they were always helpful, of
course.)

Mime
View raw message