#1127: profiling core shows incorrect filenames.
--------------------+-------------------------------------------------------
 Reporter:  coke    |       Owner:  cotto
     Type:  bug     |      Status:  new  
 Priority:  normal  |   Milestone:       
Component:  none    |     Version:       
 Severity:  medium  |    Keywords:       
     Lang:          |       Patch:       
 Platform:          |  
--------------------+-------------------------------------------------------

Comment(by cotto):

 When looking at tcllib.pbc, it appears that something's generating an
 incorrect packfile debug segment.  TclConst::class_init (in this instance,
 ymmv) lives at bytecode offsets 407 -> 417.  The bytecode debug segment
 says that tcllist.pir is responsible for this part of the bytecode.  The
 line numbers look correct, so fixing the debug segment and making sure we
 have a test to expose and cover this bug should make profiles much more
 useful.

 Since I'm responsible for the profiling runcore, consider this as much as
 note to myself as anything else. ;]

 constants table:
 {{{
     # 43:
     [ 'PFC_PMC', {
                 FLAGS    => 0x4500228
 (private3,private5,is_PMC,custom_GC,report,needs_early_gc)
                 class => Sub,
                 start_offs => 407,
                 end_offs => 417,
                 name    => 'class_init',
                 subid   => 'class_init',
                 method  => '',
                 nsentry => 'class_init',
                 namespace => 'TclConst'
                 HLL_id => 0,
     } ],
 }}}

 debug segment:
 {{{
     #6
     [
         OFFSET => 278,
         FILENAME => src/class/tcllist.pir
     ],
     #7
     [
         OFFSET => 491,
         FILENAME => src/class/tclproc.pir
     ],
 }}}

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/1127#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to