Fix incorrect uses of formatv specifiers in LLDB_LOG. Unlike Python, arguments must be numbered. All these log statements take llvm:Errors so use the LLDB_LOG_ERROR macro instead.
Details
Diff Detail
Event Timeline
These uses of LLDB_LOG are taking errors, consuming them while turning them into strings, and logging them. Unless I'm missing something, I think it would make more sense to convert these to use LLDB_LOG_ERROR.
lldb/source/Core/Debugger.cpp | ||
---|---|---|
1917–1919 | Same here. |
lldb/source/Core/Debugger.cpp | ||
---|---|---|
1917–1919 | Sorry, ignore this comment, I deleted a previous inline comment and forgot to delete this one. |
Good point, I blindly fixed the format specifiers without lookin what was being passed in.
In https://reviews.llvm.org/D154532, the string argument comes after the error. Are these interchangeable?
The 2nd argument to LLDB_LOG_ERROR is the error itself, so these should be something like LLDB_LOG_ERROR(GetLog(whatever), std::move(err), "message: {0}"); or something to this effect.
Same here.