aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorPeter Klausler <pklausler@nvidia.com>2024-10-10 10:25:19 -0700
committerGitHub <noreply@github.com>2024-10-10 10:25:19 -0700
commit4f2b65fb80a4b27e5fb88db816ed0ce174c9b1b4 (patch)
tree93eaa495517ad2a494d4979829a8fb2ad4231914 /lldb/packages/Python/lldbsuite/test/configuration.py
parentc893e3d02d1f7b67880090485a030b79741bba1c (diff)
downloadllvm-4f2b65fb80a4b27e5fb88db816ed0ce174c9b1b4.zip
llvm-4f2b65fb80a4b27e5fb88db816ed0ce174c9b1b4.tar.gz
llvm-4f2b65fb80a4b27e5fb88db816ed0ce174c9b1b4.tar.bz2
[flang] Fix references to destroyed objects (#111582)
ProgramTree instances are created as the value of a local variable in the Pre(const parser::ProgramUnit &) member function in name resolution. But references to these ProgramTree instances can persist in SubprogramNameDetails symbol table entries that might survive that function call's lifetime, and lead to trouble later when (e.g.) expression semantics needs to deal with a possible forward reference in a function reference in an expression being processed later in expression checking. So put those ProgramTree instances into a longer-lived linked list within the SemanticsContext. Might fix some weird crashes reported on big-endian targets (AIX & Solaris).
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions