stas 2002/12/09 18:49:10 Modified: src/docs/2.0/devel/debug c.pod Log: now that we have Devel::CoreDump, should use it instead of developing a new package Revision Changes Path 1.2 +4 -6 modperl-docs/src/docs/2.0/devel/debug/c.pod Index: c.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/2.0/devel/debug/c.pod,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- c.pod 9 Dec 2002 16:29:57 -0000 1.1 +++ c.pod 10 Dec 2002 02:49:10 -0000 1.2 @@ -247,15 +247,10 @@ =back -=head1 Obtaining Core Files +=head1 Analyzing Dumped Core Files META: need to review (unfinished) -=head2 ... - - -=head1 Analyzing Dumped Core Files - When your application dies with the I<Segmentation fault> error (which generates a C<SIGSEGV> signal) and optionally generates a I<core> file you can use C<gdb> or a similar debugger to find out what caused the @@ -316,6 +311,9 @@ Now the software is ready for a proper debug. =head2 Creating a Faulty Package + +META: no longer need to create the package, use C<Debug::DumpCore> +from CPAN. Need to adjust the rest of the document to use it. Next stage is to create a package that aborts abnormally with the I<Segmentation fault> error. We will write faulty code on purpose,
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
