Arnd Bergmann 2cf2f0d5b9 kdb: use memmove instead of overlapping memcpy ...

gcc discovered that the memcpy() arguments in kdbnearsym() overlap, so
we should really use memmove(), which is defined to handle that correctly:

In function 'memcpy',
    inlined from 'kdbnearsym' at /git/arm-soc/kernel/debug/kdb/kdb_support.c:132:4:
/git/arm-soc/include/linux/string.h:353:9: error: '__builtin_memcpy' accessing 792 bytes at offsets 0 and 8 overlaps 784 bytes at offset 8 [-Werror=restrict]
  return __builtin_memcpy(p, q, size);

Signed-off-by: Arnd Bergmann <[email protected]>
Signed-off-by: Jason Wessel <[email protected]>

2018-02-04 21:29:53 -06:00

..

kdb

kdb: use memmove instead of overlapping memcpy

2018-02-04 21:29:53 -06:00

debug_core.c

sched/headers: Prepare for new header dependencies before moving code to <linux/sched/nmi.h>

2017-03-02 08:42:30 +01:00

debug_core.h

kgdb/kdb: Fix no KDB config problem

2014-01-25 08:55:09 +01:00

gdbstub.c

sched/headers: Prepare for new header dependencies before moving code to <linux/sched/signal.h>

2017-03-02 08:42:29 +01:00

Makefile

…