quic_set_logger() will crash when set log level with TRACE #500
Description
A pid: 30999, tid: 31116, name: Thread-24 >>> xxx <<<
2025-08-27 22:08:03.565 31119-31119 DEBUG pid-31119 A #1 pc 000000000032dfc0 demo-0NzphHb1qgUx1io8pwsvLg==/lib/arm64/libtquic.so (offset 0x19e000)
2025-08-27 22:08:03.565 31119-31119 DEBUG pid-31119 A #2 pc 000000000032d33c demo-0NzphHb1qgUx1io8pwsvLg==/lib/arm64/libtquic.so (offset 0x19e000)
2025-08-27 22:08:03.565 31119-31119 DEBUG pid-31119 A #3 pc 000000000032d024 demo-0NzphHb1qgUx1io8pwsvLg==/lib/arm64/libtquic.so (offset 0x19e000)
2025-08-27 22:08:03.565 31119-31119 DEBUG pid-31119 A #4 pc 000000000032d024 demo-0NzphHb1qgUx1io8pwsvLg==/lib/arm64/libtquic.so (offset 0x19e000)
000000000032d024这里打印了200多次一样的信息，后面的省略了。
使用addr2line转换地址得到：
_$LT$std..path..Components$u20$as$u20$core..iter..traits..iterator..Iterator$GT$::next::h3287542f521038f6
std.b9ec7a62a4fcada1-cgu.0:0
std::io::Write::write_all_vectored::h9ac6ce22649f5dbf
std.b9ec7a62a4fcada1-cgu.0:0
_$LT$std..io..default_write_fmt..Adapter$LT$T$GT$$u20$as$u20$core..fmt..Write$GT$::write_str::h75d2cb11528bb4ad
std.b9ec7a62a4fcada1-cgu.0:0
看起来是日志的打印，在多次测试之后发现当quic_set_logger() 的日志级别设置为TRACE就会导致崩溃，而设置为DEBUG却不会