$ valgrind linuxcncrsh -- -ini /home/user/linuxcnc/configs/test1_client/test1.ini
==109918== Memcheck, a memory error detector
==109918== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==109918== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==109918== Command: linuxcncrsh -- -ini /home/user/linuxcnc/configs/test1_client/test1.ini
==109918==
Connected to foo
==109918== Thread 2:
==109918== Invalid read of size 1
==109918==    at 0x484B0B5: rawmemchr (vg_replace_strmem.c:1566)
==109918==    by 0x4C624B1: _IO_str_init_static_internal (in /usr/lib64/libc.so.6)
==109918==    by 0x4C311D5: __isoc99_sscanf (in /usr/lib64/libc.so.6)
==109918==    by 0x10EC97: getSpindle (emcrsh.cc:1630)
==109918==    by 0x10EC97: commandGet(connectionRecType*) (emcrsh.cc:2398)
==109918==    by 0x111C5F: parseCommand(connectionRecType*) (emcrsh.cc:2716)
==109918==    by 0x111E3D: readClient(void*) (emcrsh.cc:2787)
==109918==    by 0x4C66DAB: start_thread (in /usr/lib64/libc.so.6)
==109918==    by 0x4CDFA3F: clone (in /usr/lib64/libc.so.6)
==109918==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==109918==
==109918==
==109918== Process terminating with default action of signal 11 (SIGSEGV)
==109918==  Access not within mapped region at address 0x0
==109918==    at 0x484B0B5: rawmemchr (vg_replace_strmem.c:1566)
==109918==    by 0x4C624B1: _IO_str_init_static_internal (in /usr/lib64/libc.so.6)
==109918==    by 0x4C311D5: __isoc99_sscanf (in /usr/lib64/libc.so.6)
==109918==    by 0x10EC97: getSpindle (emcrsh.cc:1630)
==109918==    by 0x10EC97: commandGet(connectionRecType*) (emcrsh.cc:2398)
==109918==    by 0x111C5F: parseCommand(connectionRecType*) (emcrsh.cc:2716)
==109918==    by 0x111E3D: readClient(void*) (emcrsh.cc:2787)
==109918==    by 0x4C66DAB: start_thread (in /usr/lib64/libc.so.6)
==109918==    by 0x4CDFA3F: clone (in /usr/lib64/libc.so.6)
==109918==  If you believe this happened as a result of a stack
==109918==  overflow in your program's main thread (unlikely but
==109918==  possible), you can try to increase the size of the
==109918==  main thread stack using the --main-stacksize= flag.
==109918==  The main thread stack size used in this run was 8388608.
==109918==
==109918== HEAP SUMMARY:
==109918==     in use at exit: 682,696 bytes in 62 blocks
==109918==   total heap usage: 76 allocs, 14 frees, 697,514 bytes allocated
==109918==
==109918== LEAK SUMMARY:
==109918==    definitely lost: 8 bytes in 1 blocks
==109918==    indirectly lost: 0 bytes in 0 blocks
==109918==      possibly lost: 304 bytes in 1 blocks
==109918==    still reachable: 682,384 bytes in 60 blocks
==109918==         suppressed: 0 bytes in 0 blocks
==109918== Rerun with --leak-check=full to see details of leaked memory