on this topic, please forgive my ignorance...
don't both those settings relate to mod_perl internals?
i typically just to a
use constant DEBUG__myvar => 1 ;
and
DEBUG__myvar && print STDERR "my debug crap"
in my code to handle debugging my apps. in one of the books, it said
that anything like this:
use constant DEBUG__myvar => 0;
if ( DEBUG__myvar ){
# debug crap
}
wouldn't be compiled by startup.pl, so there wouldn't be any runtime
performance hit if debugging is coded in like that and a constant
turned it off.
On Feb 23, 2006, at 5:16 PM, Philippe M. Chiasson wrote:
Boysenberry Payne wrote:
I have a couple of question while installing MP2 over again.
Do I have to enable MP_DEBUG and MP_TRACE in order to debug
or trace; does that mean I'll be stuck with everything being
debugged or
traced?
MP_DEBUG means the compiled code will have debugging symbols
included. Typically
that translates into fatter binaries. The good thing about MP_DEBUG
is that if you
get coredumps of need to use gdb, you'll get full debug information.
MP_TRACE on the other hand, enables all the tracing code. That code
is controlled
with environment variables, and should come at a little runtime
performance hit.
----------------------------------------------------------------------
----------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG
KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32
A107 88C3A5A5
