This is an archive of the discontinued LLVM Phabricator instance.

[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
<flags> or <struct>.

Also hardcode the function names into the log messages because
if you use FUNCTION in a lambda you just get "operator()".

Diff Detail

Event Timeline

DavidSpickett created this revision.Sep 16 2022, 6:44 AM
Herald added a project: Restricted Project. · View Herald TranscriptSep 16 2022, 6:44 AM
DavidSpickett requested review of this revision.Sep 16 2022, 6:44 AM
Herald added a project: Restricted Project. · View Herald TranscriptSep 16 2022, 6:44 AM
clayborg accepted this revision.Sep 16 2022, 4:40 PM

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

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.