veyepar: Record and replay debugging with "rr"

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Debugging is expensive and not fun, especially debugging intermittent failures. rr changes that by recording Linux user-space process execution and letting you play back a recording and debug it using gdb, getting exactly the same execution as was recorded, as many times as you need. rr is used by Mozilla developers to debug Firefox, so it works on real applications. It runs on stock hardware, requires no kernel changes, and has low recording overhead (usually less than 1.5x). rr supports gdb's reverse execution features, which (combined with breakpoints and hardware data watchpoints) make debugging fast and fun. This presentation will describe how rr works, discuss some of the kernel issues that created difficulties for rr, and speculate about what we can do to make rr and related tools even better. markdown
Comment:	production notes

2016-02-04/15_39_50.dv Apply: 15:39:50 - 16:22:12 ( 00:42:22 ) S: 15:39:50 - E: 16:22:12 D: 00:42:22 show more...

vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-04/15_39_50.dv :start-time=00.0 --audio-desync=0

2016-02-04/16_22_11.dv Apply: 16:22:11 - 16:34:57 ( 00:12:46 ) S: 16:22:11 - E: 16:34:57 D: 00:12:46 show more...

vlc ~/Videos/veyepar/lca/lca2016/dv/r4mix/2016-02-04/16_22_11.dv :start-time=00.0 --audio-desync=0

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this