Use memcpy for unknown destination buffer size 19/270219/2 submit/tizen/20220127.070935
authorMichal Bloch <m.bloch@samsung.com>
Wed, 26 Jan 2022 16:01:55 +0000 (17:01 +0100)
committerMichal Bloch <m.bloch@samsung.com>
Wed, 26 Jan 2022 16:11:57 +0000 (17:11 +0100)
commit970cd407e2736c4c59774dd657a1a065f2978027
treeaaa4540d65c8cfc447e69ff57a08b7a9482af90c
parentbb64eb2960ff694e4dfebe331d13d1bbc7170d5b
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>
tests/kdbus/kdbus-util.c