This particular error, when it comes tends to come over and over and over and swamps all the other logging output. It's clearly a candidate for the verbose log channel. Since this was emitted with LLDB_LOG_ERROR that also meant it went to the always on log, where again it was swamping the other output and making logs quite difficult to read. I asked around and nobody felt the need to have this always on.