mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-11 05:55:48 +00:00
This bug shows up when callgrind dumps data of a BB with 0 instructions (the segfault only appears on x86_64; for x86 we were "lucky"). "BB with 0 instructions" happens when you switch on instrumentation (and callgrinds call graph tracing starts with an emtpy shadow call stack) in the middle of a run: Whenever the shadow callstack is empty, but callgrind sees a return instruction (ie. a shadow callstack underrun), it creates an artifical BB which is faked to have called the function we are returning from. This way, the call arc is noted and will appear in the dump. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6053