diff options
| author | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2024-08-20 15:17:40 +0800 |
|---|---|---|
| committer | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2024-08-20 15:24:35 +0800 |
| commit | 08a0dece2b2431db8abe650bb43cba01e781e1ce (patch) | |
| tree | 8591836f9b6dbaf1be5e01e085e195be815d6bd7 /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp | |
| parent | bf68e9047f62c22ca87f9a4a7c59a46b3de06abb (diff) | |
| download | llvm-08a0dece2b2431db8abe650bb43cba01e781e1ce.zip llvm-08a0dece2b2431db8abe650bb43cba01e781e1ce.tar.gz llvm-08a0dece2b2431db8abe650bb43cba01e781e1ce.tar.bz2 | |
[Coroutines] [NFCI] Don't search the DILocalVariable for __promise when constructing the debug varaible for __coro_frame
As the title mentioned, do not search for the DILocalVariable for
__promise when constructing the debug variable for __coro_frame.
This should make sense because the debug variable of `__coro_frame`
shouldn't dependent on the debug variable of `__promise`. And actually,
it is not. Currently, we search the debug variable for `__promise` only
because we want to get the debug location and the debug scope for the
`__promise`. However, we can construct the debug location directly from
the debug scope of the being compiled function. Then it is not necessary
any more to search the `__promise` variable.
And this patch makes the codes to construct the debug variable for
`__coro_frame` to be more stable. Now we will always be able to
construct the debug variable for the coroutine frame no matter if we
found the debug variable for the __promise or not.
This patch is not strictly NFC but it is intended to not affect any end
users.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions