fix: Fix sporadic test.profiling failures (#1056)

Using cut, which is always line-based, to remove bytes from a binary file can
cause problems if the binary timestamp field happens to contain a newline
character, which causes test.profiling to fail <1% of the time. Instead use tail
which has a character mode that ignores newlines.

1 files changed, 1 insertions, 1 deletions

diff --git a/test/suites/profiling.bash b/test/suites/profiling.bash
index d2bb2be8..f9043b1a 100644
--- a/test/suites/profiling.bash
+++ b/test/suites/profiling.bash
@@ -2,7 +2,7 @@
 normalize_gcno_file() {
     local from="$1"
     local to="$2"
-    cut -b 13- "${from}" >"${to}"
+    tail -c +13 "${from}" >"${to}"
 }