Stephen Gallagher <sgallagh(a)redhat.com> wrote:
>>
0003-Fixed-printing-of-undefined-value-in-sdap_async_acco.patch
>> Ticket: #579
>
> Provided that it is safe to pass a NULL pointer to fprintf(), this is
> OK. I know that glibc handles this, but I'm not entirely sure if that it
> is good behaviour (if this would work with all possible optimalizations)
> and if other libc implementations behave the same as glibc.
This is a bug in e.g. the Intel compiler, if I remember correctly.
Please fix fprintf. I recommend using the construct:
name ? name : "";
in the fprintf call.
Wouldn't it be better just to initialize the variable with "" then?