Use memcpy for unknown destination buffer size 53/270253/1
authorMichal Bloch <m.bloch@samsung.com>
Wed, 26 Jan 2022 16:01:55 +0000 (17:01 +0100)
committerHyotaek Shim <hyotaek.shim@samsung.com>
Thu, 27 Jan 2022 06:47:09 +0000 (06:47 +0000)
commit5873408a2ff53f958511e602f155abfff32b1586
treeaaa4540d65c8cfc447e69ff57a08b7a9482af90c
parented6b7f2672c98b1f35bd5ab70789e06cde188222
Use memcpy for unknown destination buffer size

Since we're using the source length instead
of destination size, use memcpy instead.

This is because the compiler realizes that this
should've been implemented via strcpy (without N)
and issues a warning, but then Tizen tools for
static analysis complain about regular strcpy.

Change-Id: I51b0b1e52bc221a972ac8863d3f82ac15f199dac
Signed-off-by: Michal Bloch <m.bloch@samsung.com>
(cherry picked from commit 970cd407e2736c4c59774dd657a1a065f2978027)
tests/kdbus/kdbus-util.c