On Sun, Sep 25, 2016 at 11:23 PM, Daniel Stenberg <dan...@haxx.se> wrote: > On Fri, 23 Sep 2016, David Drysdale wrote: > >> I can't reproduce the problem, so could you try doing a non-valgrind debug >> build and seeing what pops out in the debugger (e.g. libtool --mode=execute >> gdb ./arestest)? The stack makes it look like a null pointer is being >> passed down, only it's for a C++ reference rather than a pointer so that >> seems odd... > [snip] > > Any idea what I should try there?
I could reproduce the problem once I spun up a VM with gcc 6.2 on it, so I went hunting and found: https://github.com/google/googletest/issues/705#issuecomment-235067917 I've pushed a commit with that change in it, so hopefully things should work for you now... D.