Revision: 954
Author: [email protected]
Date: Wed Dec 16 09:56:07 2009
Log: for_chunks SUB_CALLERS was not passing the callback the caller name.
Added at the end of the list of parameters, to avoid breaking code relying  
on
the existing order.
http://code.google.com/p/perl-devel-nytprof/source/detail?r=954

Modified:
  /trunk/NYTProf.xs
  /trunk/lib/Devel/NYTProf/ReadStream.pm

=======================================
--- /trunk/NYTProf.xs   Wed Dec 16 07:18:11 2009
+++ /trunk/NYTProf.xs   Wed Dec 16 09:56:07 2009
@@ -4331,6 +4331,7 @@
                      sv_setnv(cb_args[i], reci_time);       
XPUSHs(cb_args[i++]);
                      sv_setiv(cb_args[i], rec_depth);       
XPUSHs(cb_args[i++]);
                      sv_setsv(cb_args[i], called_subname_sv);      
XPUSHs(cb_args[i++]);
+                    sv_setsv(cb_args[i], caller_subname_sv);      
XPUSHs(cb_args[i++]);
                      assert(i <= C_ARRAY_LENGTH(cb_args));

                      PUTBACK;
=======================================
--- /trunk/lib/Devel/NYTProf/ReadStream.pm      Wed Dec 16 08:43:25 2009
+++ /trunk/lib/Devel/NYTProf/ReadStream.pm      Wed Dec 16 09:56:07 2009
@@ -183,7 +183,7 @@
  the perl subroutines defined in all the files visited while profiling.
  See also C<%DB::sub> in L<perldebguts>.

-=item SUB_CALLERS => $fid, $line, $count, $incl_time, $excl_time,  
$ucpu_time, $scpu_time, $reci_time, $rec_depth, $name
+=item SUB_CALLERS => $fid, $line, $count, $incl_time, $excl_time,  
$ucpu_time, $scpu_time, $reci_time, $rec_depth, $name, $caller_name

  At the end of the run the profiler will output chunks that report on
  where subroutines were called from.

-- 
You've received this message because you are subscribed to
the Devel::NYTProf Development User group.

Group hosted at:  http://groups.google.com/group/develnytprof-dev
Project hosted at:  http://perl-devel-nytprof.googlecode.com
CPAN distribution:  http://search.cpan.org/dist/Devel-NYTProf

To post, email:  [email protected]
To unsubscribe, email:  [email protected]

Reply via email to