> if -X causes DEBUG to be defined and prefork uses that as a hint to do
> ONE_PROCESS, that sounds perfectly fine to me.
Me too. +1 on the patch.
> and when will unix thread debugging catch up with the 1980s? i was
> debugging multithreaded programs with ease on OS/2 1.x over a decade ago.
>
> btw, even though -X exists, i frequently debug apache 1.3 by restricting
> it to a single child process and attaching to that child... because some
> of the -X changes alter the behaviour.
Yep, which is why I was surprised to hear that ONE_PROCESS was causing
NO_DETACH to be set as well -- that doesn't make any sense to me. There
is nothing more frustrating for me than being in the middle of a "how to
debug apache" class and having to explain these new options. ONE_PROCESS
should mean only one child process, since that's exactly what a developer
needs to attach to a child before a request is sent. -X should mean that
we are inside a debugger and need all of the options to make stepping
though a process easy.
....Roy
