--- 1 ---
--- 1 ---

one of the supported debuggers can be invoked via the -debug switch:

e.g.: run with the defaults: gdb

  % ./t/TEST -debug

or use ddd:

  % ./t/TEST -debug=ddd

Note that currently we tell 'ddd' to internally use 'gdb'.

--- 2 ---

--breakpoint : set as many breakpoint as needed by repeating the key

e.g:

  % ./t/TEST -debug -breakpoint=modperl_cmd_switches \
     -breakpoint=modperl_cmd_options

will set the 'modperl_cmd_switches' and 'modperl_cmd_options'
breakpoints and run the debugger. But first it'll set the
'ap_run_pre_config' breakpoint and run till there, since without it we
cannot set breakpoints in mod_perl code if it's loaded via DSO.

If you want to tell the debugger to jump to the start of the mod_perl
code you may run:

  % ./t/TEST -debug -breakpoint=modperl_hook_init

In fact --breakpoint automatically turns on the debug mode, so you can
run:

  % ./t/TEST -breakpoint=modperl_hook_init

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: b4be4a41b2a3352907de631eb6da1671a2f7b614@68478 13f79535-47bb-0310-9956-ffa450edef68

Distrotech/mod_perl,Distrotech/mod_perl,Distrotech/mod_perl,Distrotech/mod_perl