Björn Fahller

Nope, --skip-solibs does not help. I also changed the build so that it compiles kcov with the same compiler it builds the test program with, still with the same result.

Unfortunately I can't reproduce the problem myself either, but it consistently happens on every build in the travis-ci containers. I really don't know how to get the necessary information out...

OK, this has now gotten weird for real. The problem now shows both with clang++ 3.6 and 3.7. The v12 tagged builds crashed with SIGSEGV on the kcov runs for...

clang++ allows you to specify which version of dwarf debug info to produce (2, 3 or 4.) Would it make a difference for kcov which is generated?

By running kcov inside gdb in the travis build, I managed to capture this back trace. This is after the test program has successfully run to completion. ``` Program received...

Late followup, but maybe this symbol demangler bug is relevant? https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909

It depends on what you mean. If you mean, to hijack an existing member function for the purposes of testing, then that is not possible. *Trompeloeil* generates valid C++ code...

I don't think I understand what you want to achieve. The example above creates a non-virtual function named `mock_func`. The only reason mocking functions from interfaces become virtual is because...

Nothing needs to be virtual, as I have shown in the two examples above. It's a very common use case that a function is, but there's no such need. In...

It is the way it must be, unless some kind of back tracking is implemented (and since a matching call can have side effects, I don't think backtracking is possible.)...