On Sat, 31 Jul 2021 at 07:33, Paolo Bonzini wrote:
>
> Coverity seems to have issues figuring out the properties of g_malloc0
> and other non *_n functions. While this was "fixed" by removing the
> custom second argument to __coverity_mark_as_afm_allocated__, inline
> the code from the array-base
Coverity seems to have issues figuring out the properties of g_malloc0
and other non *_n functions. While this was "fixed" by removing the
custom second argument to __coverity_mark_as_afm_allocated__, inline
the code from the array-based allocation functions to avoid future
issues.
Signed-off-by:
