1*6d3d952fSTomer Shafir#RUN: not llvm-xray account %s -o - -m %S/Inputs/simple-instrmap.yaml -d 2>&1 | FileCheck %s 2*6d3d952fSTomer Shafir#RUN: llvm-xray account %s -k -o - -m %S/Inputs/simple-instrmap.yaml -d 2>&1 | FileCheck %s --check-prefix=KEEPGOING 3*6d3d952fSTomer Shafir 4*6d3d952fSTomer Shafir--- 5*6d3d952fSTomer Shafirheader: 6*6d3d952fSTomer Shafir version: 1 7*6d3d952fSTomer Shafir type: 0 8*6d3d952fSTomer Shafir constant-tsc: true 9*6d3d952fSTomer Shafir nonstop-tsc: true 10*6d3d952fSTomer Shafir cycle-frequency: 0 11*6d3d952fSTomer Shafirrecords: 12*6d3d952fSTomer Shafir# We simulate the case when, for whatever reason, we see that a thread's stack 13*6d3d952fSTomer Shafir# is empty when we see an EXIT record. This can happen for example when an 14*6d3d952fSTomer Shafir# instrumented function does a 'fork()', where the child process will not see 15*6d3d952fSTomer Shafir# the entry record but see the exit record. This is completely valid data, 16*6d3d952fSTomer Shafir# which should be handled with grace (i.e. we treat it as an error, but since 17*6d3d952fSTomer Shafir# the llvm-xray account tool has an option to keep going, gives the user a 18*6d3d952fSTomer Shafir# chance to retry). 19*6d3d952fSTomer Shafir - { type: 0, func-id: 1, cpu: 1, thread: 1, kind: function-exit, tsc: 10000} 20*6d3d952fSTomer Shafir... 21*6d3d952fSTomer Shafir 22*6d3d952fSTomer Shafir#CHECK: Error processing record: {{.*}} 23*6d3d952fSTomer Shafir#CHECK-NEXT: Thread ID: 1 24*6d3d952fSTomer Shafir#CHECK-NEXT: (empty stack) 25*6d3d952fSTomer Shafir#CHECK-NEXT: llvm-xray: Failed accounting function calls in file '{{.*}}'. 26*6d3d952fSTomer Shafir 27*6d3d952fSTomer Shafir#KEEPGOING: Error processing record: {{.*}} 28*6d3d952fSTomer Shafir#KEEPGOING-NEXT: Thread ID: 1 29*6d3d952fSTomer Shafir#KEEPGOING-NEXT: (empty stack) 30