Unexpected segfault in a test happily passes #145

Something in the new syscall buffer code is tripping a segfault, but since it's in the child process, the rr test harness happily records and replays it faithfully. It would be nice to catch these bugs without overcontraining execution. My best idea so far is to supply an output token that grep needs to find in the recorded output, like "FINISHED".