Suricata

Looks like we recursively try to add debug output from the debug logging path.

$ SC_LOG_LEVEL=Debug gdb --args ./src/suricata -c suricata.yaml -l tmp -k none --disable-detection -r ~/devel/suricata-verify/tests/alert-testmyids/input.pcap 
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./src/suricata...
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file /home/victor/sync/devel/eidps/src/suricata.
Use `info auto-load python-scripts [REGEXP]' to list them.
(gdb) r
Starting program: /home/victor/sync/devel/eidps/src/suricata -c suricata.yaml -l tmp -k none --disable-detection -r /home/victor/devel/suricata-verify/tests/alert-testmyids/input.pcap
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x0000555555ce06af in SCLog (x=<error reading variable: Cannot access memory at address 0x7fffff7fe8cc>, file=<error reading variable: Cannot access memory at address 0x7fffff7fe8c0>, func=<error reading variable: Cannot access memory at address 0x7fffff7fe8b8>, line=<error reading variable: Cannot access memory at address 0x7fffff7fe8c8>, module=<error reading variable: Cannot access memory at address 0x7fffff7fe8b0>, fmt=<error reading variable: Cannot access memory at address 0x7fffff7fe8a8>) at util-debug.c:727
727    {
(gdb) bt
#0  0x0000555555ce06af in SCLog (x=<error reading variable: Cannot access memory at address 0x7fffff7fe8cc>, file=<error reading variable: Cannot access memory at address 0x7fffff7fe8c0>, 
    func=<error reading variable: Cannot access memory at address 0x7fffff7fe8b8>, line=<error reading variable: Cannot access memory at address 0x7fffff7fe8c8>, 
    module=<error reading variable: Cannot access memory at address 0x7fffff7fe8b0>, fmt=<error reading variable: Cannot access memory at address 0x7fffff7fe8a8>) at util-debug.c:727
#1  0x0000555555cfdbd8 in TimeGet () at util-time.c:172
#2  0x0000555555ce0306 in SCLogMessage (log_level=SC_LOG_DEBUG, file=0x555557028d81 "util-time.c", line=172, function=0x555557028eb8 <__FUNCTION__.1> "TimeGet", module=0x555557028d60 "util-time", 
    message=0x7fffff7ffad0 "time we got is 1675236740 sec, 676047 usec") at util-debug.c:669
#3  0x0000555555ce0824 in SCLog (x=7, file=0x555557028d81 "util-time.c", func=0x555557028eb8 <__FUNCTION__.1> "TimeGet", line=172, module=0x555557028d60 "util-time", 
    fmt=0x555557028da8 "time we got is %lu sec, %lu usec") at util-debug.c:740
#4  0x0000555555cfdbd8 in TimeGet () at util-time.c:172
#5  0x0000555555ce0306 in SCLogMessage (log_level=SC_LOG_DEBUG, file=0x555557028d81 "util-time.c", line=172, function=0x555557028eb8 <__FUNCTION__.1> "TimeGet", module=0x555557028d60 "util-time", 
    message=0x7fffff800cb0 "time we got is 1675236740 sec, 676041 usec") at util-debug.c:669
#6  0x0000555555ce0824 in SCLog (x=7, file=0x555557028d81 "util-time.c", func=0x555557028eb8 <__FUNCTION__.1> "TimeGet", line=172, module=0x555557028d60 "util-time", 
    fmt=0x555557028da8 "time we got is %lu sec, %lu usec") at util-debug.c:740
#7  0x0000555555cfdbd8 in TimeGet () at util-time.c:172