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 $ENV{MP_DEBUGGER} || 'gdb'. And:
>
> --debug=db_foo
>
> uses 'db_foo' if supported and quits with an error if not.
that would be great.
> Anyway, ddd coupled with gdb should be invoked as:
> my $command = qq{ddd --gdb --debugger "gdb -command $file" $config->{vars}->{httpd}};
>
> I use ddd since it's a fantastic tool when you need to debug/learn
> complicated data structures. Its 'Data' window is very helpful.
i'll have to try ddd one of these days.
> Probably another useful key would be -debug-jump-init or similar which
> will take you right into the modperl_hook_init() via the breakpoint. I'm
> adding your trick notes to modperl_dev.pod, but I think it'd be nice to
> have the feature in core. I can also think of having a set of jump points
> to various frequently used breakpoints selected via the debug options, but
> this can be added later if found useful.
that would be cool too.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
