Good question, I unfortunately don't have the code in the exact state to trigger that specific bug anymore (I fixed the issue with gdb/swift demangle...) but will see if I can make it happen again. I basically run into tons of asserts currently (read: every single time I run lddb currently) with both 5.3.3 and 5.4 dev snapshot on Linux, I'd be happy to capture additional information (or providing you with source snapshot/branch that reproduces - I'm just working on SwiftNIO so it can be freely shared, but a few prerequisites on the runtime environment (Ubuntu 20.04, updated kernel to 5.11 and liburing installed) - let me know if that is something you want to pursue and I will simply branch/tag the WIP if you want a full reproducible environment.
Environment
jocke@swift511 ~/s/swiftnio511 (jh-liburing-refactor-selector) [SIGILL]> uname -a
Linux swift511 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
jocke@swift511 ~/s/swiftnio511 (jh-liburing-refactor-selector)> swift --version
Swift version 5.3.3 (swift-5.3.3-RELEASE)
Target: x86_64-unknown-linux-gnu
jocke@swift511 ~/s/swiftnio511 (jh-liburing-refactor-selector)>
Additional Detail from JIRA
md5: f90b5fbd68ebd9e5b087e76b0a14b24d
Issue Description:
lldb-swift aborted when doing "po xxx"
Will attach link to reproducer.
The text was updated successfully, but these errors were encountered: