bitcoin-qt core dumping #4410

I'm struggling to find the cause of this error. Can anyone recommend how to better use gdb to find the source of the error please?

EXCEPTION: St13runtime_error
tinyformat: Not enough conversion specifiers in format string
bitcoin in msghand

terminate called after throwing an instance of 'std::runtime_error' what(): tinyformat: Not enough conversion specifiers in format string

Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffb1639700 (LWP 3360)] 0x00007ffff4158425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff4158425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff415bb8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff4aac69d in __gnu_cxx::__verbose_terminate_handler() ()

from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x00007ffff4aaa846 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x00007ffff4aaa873 in std::terminate() ()

from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x00007ffff4aaa9b6 in __cxa_rethrow ()

from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x0000555555774d5f in TraceThread<void (*)()> (

name=0x555555c11beb "msghand", func=<optimized out>) at util.h:559

#7 0x00007ffff7546ce9 in thread_proxy ()

from /usr/lib/libboost_thread.so.1.46.1 #8 0x00007ffff58cce9a in start_thread ()

from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x00007ffff42163fd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x0000000000000000 in ?? ()

(gdb)

On first glance, looks like a LogPrintf gone bad. 'thread apply all bt' would tell more.

This is not a core dump but an exception. You are back-tracing the place where it is caught not where is is raised.

You could debug this either by adding more information to the exception message (it is raised in tinyformat.h:675), setting a breakpoint where it is raised, or by adding a catchpoint in gdb (catch throw <regexp>), see https://sourceware.org/gdb/onlinedocs/gdb/Set-Catchpoints.html

The issue was using LogPrintf instead of LogPrint - strangely this causes a runtime error rather than a compile error - not ideal