On Mon, Sep 26, 2016 at 09:34:15AM -0600, Jeff Law wrote:
> On 09/26/2016 09:20 AM, Florian Weimer wrote:
> >* Jeff Law:
> >
> >>On 09/25/2016 03:46 AM, Bernd Edlinger wrote:
> >>>Hi Martin,
> >>>
> >>>in the past I have seen (and fixed) code like
> >>>
> >>>sprintf(buf, "%s %d", buf, x);
> >>>
>
On 09/26/2016 09:20 AM, Florian Weimer wrote:
* Jeff Law:
On 09/25/2016 03:46 AM, Bernd Edlinger wrote:
Hi Martin,
in the past I have seen (and fixed) code like
sprintf(buf, "%s %d", buf, x);
that may possibly work by chance, but usually
produces undefined results.
Do you see a way to
* Jeff Law:
> On 09/25/2016 03:46 AM, Bernd Edlinger wrote:
>> Hi Martin,
>>
>> in the past I have seen (and fixed) code like
>>
>> sprintf(buf, "%s %d", buf, x);
>>
>> that may possibly work by chance, but usually
>> produces undefined results.
>>
>> Do you see a way to enhance the warning for
On 09/25/2016 03:46 AM, Bernd Edlinger wrote:
Hi Martin,
in the past I have seen (and fixed) code like
sprintf(buf, "%s %d", buf, x);
that may possibly work by chance, but usually
produces undefined results.
Do you see a way to enhance the warning for cases
where the output buffer overlaps
On 9/25/16, Bernd Edlinger wrote:
> Hi Martin,
>
> in the past I have seen (and fixed) code like
>
> sprintf(buf, "%s %d", buf, x);
>
> that may possibly work by chance, but usually
> produces undefined results.
>
> Do you see a way to enhance the warning for cases
>