Philippe M. Chiasson wrote:
Happened onto the cute Devel::GDB module and quickly wiped out a patch to make
t/REPORT attempt to automatically generate back traces for core files it finds in t/


Any interest in this ?

Excellent!

Though I doubt that anybody will have this optional module installed. I wish we could find a good way to suggest all the optional modules one wants to install (there are quite a few needed to have 'make test' not skip some tests).

BTW, there is also http://search.cpan.org/dist/Debug-FaultAutoBT/ but it has some problems sometimes :) But I don't think we need it, since normally we get the core dumped (with the exception to some OSes)

but please drop the spaces in the core_dump code. Thanks...

+sub core_dump {
+ my $self = shift;
+
^^^^^^^^
and below
+ $core_dump = "";
+ + if ( eval { require Devel::GDB } ) {
+ find(\&dump_core_file, 't')
+ }
+ + $core_dump ||= '[CORE TRACE COMES HERE]';
+

I've tested that only with threaded, will the below work with prefork too? I mean all the threads stuff in gdb commands?


> +    $core_dump .= join '',
> +           $gdb->get("file $httpd"),
> +           $gdb->get('sharedlibrary'),
> +           $gdb->get("core $core"),
> +           $gdb->get('info threads'),
> +           $gdb->get('thread apply all bt');
> +}


-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to