Closed peddie closed 6 years ago
Oops, I guess I never responded to this! I think I fixed this bug a few months back: I remember being able to reproduce this issue when I first saw this bug report, but now Herbgrind seems to run without crashing on the program in question.
Unfortunately, Herbgrind doesn't recognize the C++ idiom of using cout streams to print, so it doesn't see the outputs currently. Eventually, I'll try to fix this, but for now you could insert a "printf", or simply use the HERBGRIND_MARK_IMPORTANT macro to mark your output. I think the latter should basically have no runtime effect when not run under Herbgrind (it inserts a little block of assembly which is a no-op, but is recognized by Herbgrind).
If the output recognition is important to you, feel free to file another issue, and I'll keep it on my todo list.
I realize this might be out of scope for the current development focus of
herbgrind
, but I thought I'd report it anyway for completeness.I've run the following example program:
built with the following command:
and I receive the expected output:
If I add
-march=ivybridge
to my compile command, all is well, but if I go one more step to-march=haswell
,herbgrind
dies with a failed assertion (full transcript below):It would be nice to be able to run the exact binary I want to use in production under
herbgrind
.Here is the full error transcript: