On Wed, 18 Jul 2001, Doug MacEachern wrote:
On Thu, 19 Jul 2001, Stas Bekman wrote:
now -debug will always set the apr_dso_load and modperl_hook_init bp and
run after these.
i think you misunderstood my comment before. no breakpoints should
be set by default, only when -breakpoint is
looks great stas, feel free to commit.
there's just one style nit
if () {
} else {
}
which should be:
if () {
else {
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Thu, 19 Jul 2001, Doug MacEachern wrote:
looks great stas, feel free to commit.
there's just one style nit
if () {
} else {
}
which should be:
if () {
else {
}
doh! habits, habits
I'd install per-commit filter to croak on the '} else {' pattern :)
thanks for reminder
On Thu, 19 Jul 2001, Stas Bekman wrote:
now -debug will always set the apr_dso_load and modperl_hook_init bp and
run after these.
i think you misunderstood my comment before. no breakpoints should
be set by default, only when -breakpoint is specified. and rather than
using apr_dso_load to
On Sat, 14 Jul 2001, Stas Bekman wrote:
doable. I know you don't want to lose -d shortcut :)
yeah :)
I'm not sure what's the definition of 'always'. There are cases where you
run -d to debug the segfault and you want the debugger to 'run' till the
segfault without any breakpoints.
On Sun, 15 Jul 2001, Doug MacEachern wrote:
On Sat, 14 Jul 2001, Stas Bekman wrote:
doable. I know you don't want to lose -d shortcut :)
yeah :)
I'm not sure what's the definition of 'always'. There are cases where you
run -d to debug the segfault and you want the debugger to 'run'
On Wed, 11 Jul 2001, Stas Bekman wrote:
% ./t/TEST -debug -debugger=ddd
how about reusing the current -debug: t/TEST -d ddd ?
--debug-hook_init : bring the debugger to the 'modperl_hook_init'
function via the breakpoint (internally it first loads the mod_perl
DSO module via
On Mon, 9 Jul 2001, Doug MacEachern wrote:
On Sun, 8 Jul 2001, Stas Bekman wrote:
Doug, how do we want to change the start_gdb with a more generic code and
decide which debugger is to be used via the command line option and/or env
var?
I suggest that we have 'debug:s' option,
On Sun, 8 Jul 2001, Stas Bekman wrote:
Doug, how do we want to change the start_gdb with a more generic code and
decide which debugger is to be used via the command line option and/or env
var?
I suggest that we have 'debug:s' option, where:
--debug
(no value) uses
Doug, how do we want to change the start_gdb with a more generic code and
decide which debugger is to be used via the command line option and/or env
var?
I suggest that we have 'debug:s' option, where:
--debug
(no value) uses $ENV{MP_DEBUGGER} || 'gdb'. And:
--debug=db_foo
uses 'db_foo'
10 matches
Mail list logo
