gistfile1.txt

==19193== Memcheck, a memory error detector
==19193== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==19193== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info
==19193== Command: /tmp/kbd/tests/libkbdfile/.libs/libkbdfile-test13
==19193==

vex: priv/host_ppc_defs.c:6712 (chainXDirect_PPC): Assertion `isLoadImm_EXACTLY2or5(p, 30, (Addr)disp_cp_chain_me_EXPECTED, mode64, endness_host)' failed.
vex storage: T total 275633592 bytes allocated
vex storage: P total 192 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==19194==    at 0x58064220: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x580643EF: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x5806467B: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x580646CB: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x58089567: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x581BD89B: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x582BA22F: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x581BC817: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x58091957: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x580E5E67: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x580E9E4F: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)
==19194==    by 0x5814C597: ??? (in /usr/libexec/valgrind/memcheck-ppc64le-linux)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 19194)
==19194==    at 0x48B6D44: memcpy (in /usr/libexec/valgrind/vgpreload_memcheck-ppc64le-linux.so)
==19194==    by 0x49799B7: memcpy (string_fortified.h:29)
==19194==    by 0x49799B7: __libc_sigaction (libc_sigaction.c:66)
==19194==    by 0x4A7508B: __spawni_child (spawni.c:132)
==19194==    by 0x4A99843: clone (clone.S:107)
client stack range: ??????? client SP: 0x492FB70
valgrind stack range: [0x1009260000 0x100935FFFF] top usage: 20464 of 1048576


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

==19193==
==19193== HEAP SUMMARY:
==19193==     in use at exit: 0 bytes in 0 blocks
==19193==   total heap usage: 21 allocs, 21 frees, 136,431 bytes allocated
==19193==
==19193== All heap blocks were freed -- no leaks are possible
==19193==
==19193== For lists of detected and suppressed errors, rerun with: -s
==19193== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)