Thanks, yes, i am currently prototyping. For simplicity i process all pushes to a stack. Once a pop comes in i will store the stack data. Thus i get the stack usage over execution time. By simply appending the functions to each other i can use regex for matching without big effort. In the end it is simpler than expected :-)

Here my prototype in case of interrest

package CallStackAnalyzer;

use strict;
use warnings;
use diagnostics;

sub new {
  my $self = {
    name              => 'CallStackAnalyzer',
    tracefilecontent  => undef,
    stack             => [],
    stacktraces       => {},
    direction         => '',
  };
  bless $self;
  return $self;
}

sub TraceFile{
  my $self                      = shift;
  $self->{tracefilecontent}  = shift;  
  _AnalyzeTraceFile($self);
}

sub _AnalyzeTraceFile{
  my $self = shift;
  my @trace = @{$self->{tracefilecontent}};
  foreach my $line (@trace){    
    if($line=~m/^(ENTRY):\s+\S+\s+\S+\s+(\S+)\(\)/){      
      push(@{$self->{stack}}, $2) && ($self->{direction} = 'up');
    } elsif ($line=~m/^(EXIT):\s+\S+\s+\S+\s+(\S+)\(\)/){
      my @stack = $self->{stack};
      ($self->{stacktraces}{join('->',@{$self->{stack}})} = \@stack )
        && ($self->{direction} = 'down') 
        if( not $self->{direction} eq 'down');
      pop(@{$self->{stack}});
    }       
  }
  return ;
}
1;

package TraceCallStack;

use strict;
use warnings;
use diagnostics;
use CallStackAnalyzer;


sub Main{
  my $trace = open(FH, "CallStack.txt");
  my @tracecontent = <FH>;
  close FH;
  my $CSA = CallStackAnalyzer->new();
  $CSA->TraceFile(\@tracecontent);
  
  return;
}


Main();

1;
[download]

It works out great. I will add one more interface to do the matching against a collection of functions..
Many thanks!!!

Tobias