Trace length

Juraj Oršulić juraj.orsulic at
Thu Jul 20 11:54:56 UTC 2017

Great, thanks for the lightning-quick response :-)


On Thu, Jul 20, 2017 at 8:44 AM, Robert O'Callahan <robert at>

> On Thu, Jul 20, 2017 at 6:41 PM, Juraj Oršulić <juraj.orsulic at>
> wrote:
>> Hello! I have a bunch of recorded traces (all of the same bug). I am
>> trying to find the one with shortest wall time needed to trigger the bug
>> (the bug causes an immediate SIGABRT, so I don't need anything fancy, just
>> the complete wall time of each trace). Is this available somewhere in trace
>> metadata, or can be estimated from tick counts, without running the
>> complete trace?
> If you run `rr dump` on each trace then you will see a 'real_time' field
> in each trace record. Subtracting the first value from the last value will
> give you the total time required to record the trace, and choosing trace
> with the shortest recording time is probably what you want.
> Rob
> --
> lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
> toD
> selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
> rdsme,aoreseoouoto
> o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
> lurpr
> .a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt
> sstvr  esn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the rr-dev mailing list