This happens if the type is described elsewhere in target xml as a
<flags> or <struct>.
Also hardcode the function names into the log messages because
if you use FUNCTION in a lambda you just get "operator()".
Paths
| Differential D134043
[lldb] Log when we cannot find an equivalent for a gdb register type ClosedPublic Authored by DavidSpickett on Sep 16 2022, 6:44 AM.
Details Summary This happens if the type is described elsewhere in target xml as a Also hardcode the function names into the log messages because
Diff Detail
Event TimelineComment Actions So you can use __PRETTY_FUNCTION__ in log messages if you want to get a demangled name for a C++ function, but that includes args, so it might be too verbose in a log message. This revision is now accepted and ready to land.Sep 16 2022, 4:40 PM Comment Actions I didn't know about that, it's exactly what I wanted - if it worked with msvc https://godbolt.org/z/cqYf3c39n. It is used in lldb but only in tests we know will be compiled with clang (well, we assume) and some Mac OS native code which will be clang compiled. Closed by commit rGec3e290502db: [lldb] Log when we cannot find an equivalent for a gdb register type (authored by DavidSpickett). · Explain WhySep 20 2022, 2:27 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 460734 lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
|
clang-format not found in user’s local PATH; not linting file.