[Lldb-commits] [lldb] [lldb] Don't crash in DIL on an operand with no type system (PR #226908)
Ilia Kuklin via lldb-commits
lldb-commits at lists.llvm.org
Mon Sep 28 09:51:48 PDT 2026
kuilpd wrote:
> Having some default rather than just failing is more useful behavior. When you are stopped in a frame w/o an obvious typesystem, you are probably going to be running some global routines or looking at global data. If most of system code is C++ having that be the fallback makes sense, but as more system code moves to other languages, maybe this is something we should let users set?
>
> We have a `set set target.language` that forces a language, but that overrides the language detected in a frame, so it's too draconian for a default state of lldb. Maybe `set set target.fallback-language` or something like that?
>
> Anyway, yes we should have the same fallback for DIL and expr, the only question is whether that should be user settable or just be C++ for now.
If this is causing issues somewhere right now, we can make a quick fallback to C++ here. I can make a patch later that introduces the option and the according logic to DIL.
https://github.com/llvm/llvm-project/pull/226908
More information about the lldb-commits
mailing list