Displaying 3 results from an estimated 3 matches for "fqux".
Did you mean:
flux
2018 Nov 26
2
Source locations missing when using xray-account
...ount -sort=sum -sortorder=dsc -instr_map ./llvm xray-log.llvm.hgD9oi
Functions with latencies: 5
funcid count [ min, med, 90p, 99p,
max] sum function
6 9 [ 0.000006, 0.000006, 0.000040, 0.000040,
0.000040] 0.000089 <invalid>:0:0: fqux
... 4 lines omitted
If I then inspect the executable with llvm-dwarfdump, I can see that
the debug information for fqux clearly lists the location as well.
0x00000918: DW_TAG_subprogram
DW_AT_low_pc (0x00000000004207c8)
DW_AT_high_pc (0x0000000000420817)...
2018 Dec 03
2
Source locations missing when using xray-account
...ray-log.llvm.hgD9oi
>>
>> Functions with latencies: 5
>> funcid count [ min, med, 90p, 99p,
>> max] sum function
>> 6 9 [ 0.000006, 0.000006, 0.000040, 0.000040,
>> 0.000040] 0.000089 <invalid>:0:0: fqux
>> ... 4 lines omitted
>>
>> If I then inspect the executable with llvm-dwarfdump, I can see that
>> the debug information for fqux clearly lists the location as well.
>>
>> 0x00000918: DW_TAG_subprogram
>> DW_AT_low_pc (0x00000000004207...
2018 Dec 06
2
Source locations missing when using xray-account
...t; Functions with latencies: 5
>> >> funcid count [ min, med, 90p, 99p,
>> >> max] sum function
>> >> 6 9 [ 0.000006, 0.000006, 0.000040, 0.000040,
>> >> 0.000040] 0.000089 <invalid>:0:0: fqux
>> >> ... 4 lines omitted
>> >>
>> >> If I then inspect the executable with llvm-dwarfdump, I can see that
>> >> the debug information for fqux clearly lists the location as well.
>> >>
>> >> 0x00000918: DW_TAG_subprogram
>...