I don't think I've seen an issue raised for this - it's more of a development issue than a runtime issue but if encounter it often, which is that if there is an incorrect number of arguments in a LogPrint() or LogPrintf() then no compile error/warning is given, it will cause the code to SIGABRT, and a gdb backtrace never provides much useful information about where the error in the code is. Only the name of the thread is given which can often leave a lot of searching or git bisecting. This common problem could be made easier to debug...