Rúbio Terra

This would make a very good addition. I've had to write these boilerplate several times.

You can by using a custom fake fuction: For instance: ```c FAKE_VALUE_FUNC_VARARG(int, fprintf, FILE *, const char*, ...); ``` In order to access the variadic parameters from your custom fake...

You're talking about the call history, right? The problem is the variadic arg types are not known, so there's no way to declare an array to automatically store them. But...

This is brilliant! This always annoyed me as well. **Why isn't this merged yet?** Now, is there any reason the code for `FFF_RESET_CALLED_FAKES` should not be called automatically from `FFF_RESET_HISTORY`?...

It seems you're just declaring the mock, but not defining it. You either have to use `FAKE_VALUE_FUNC_VARARG`, which directly defines your mock function, or use the pair `DEFINE_FAKE_VALUE_FUNC_VARARG`/`DECLARE_FAKE_VALUE_FUNC_VARARG` if you...

I just opened a [pull request](https://github.com/meekrosoft/fff/pull/98) to fix this warning, so you won't need to use `FAKE_VALUE_FUNC0` anymore.

Ah, yes, sorry.

This is the same as #11326. The problem also shows for remote WSL connections.

This happens for all releases since v1.17.2 for all member of my team (some 5-10 guys). It happens for local Ubuntu users and WSL users. A comparison between v.1.16.3 and...

@Colengms, we cross compile to a specific embedded system using gcc 12.2.0. But I don't think the cross-compiler is the problem, because the code should be valid for other configurations...