I just tested this bug using packages from https://apt.llvm.org/ . I see
that the bug reproduces with lldb-15, but doesn't reproduce with
lldb-16. So let's just wait when lldb 16 enters debian, and the bug
will be hopefully fixed

-- 
Askar Safin

Reply via email to