That doesn't do much to test correctness, though certainly testing that it
doesn't crash is a start. I'm not sure it's really worthwhile to have a
separate program for this. You can drive that code by running
"eu-unstrip -n --core=FILE" and also check the output for the expected
You won't really be testing much unless you try it with a wide variety of
different core file contents. Unfortunately, I didn't really keep track
when hacking on that code of all the cases that ought to be tested.
Looking at comments in the uncovered code may give you some clues.