A RichManglingContext constructed with an invalid demangled name or with a demangled function name without any context will have an empty context. This triggers an assertion in RichManglingContext::GetBufferRef() when debugging a native Windows process on x86 when it shouldn't. Remove the assertion.
Details
Details
- Reviewers
aleksandr.urakov zturner lldb-commits - Commits
- rG2fc9c3b05f3f: [lldb] Remove an assertion in RichManglingContext::GetBufferRef() hit when…
rLLDB343292: [lldb] Remove an assertion in RichManglingContext::GetBufferRef() hit when…
rL343292: [lldb] Remove an assertion in RichManglingContext::GetBufferRef() hit when…
Diff Detail
Diff Detail
Event Timeline
Comment Actions
BTW, I wrote a demangler for Windows ABI that should be 100% complete modulo bugs and can generate an AST that RichManglingContext should use. So it would be interesting if someone decided to start using that to make this actually work.