DavidSpickett wrote: > Log errors to the system log if they would otherwise get dropped
Dropped because of what exactly, because the user did not enable a channel that would include them? How does one enable collection of these with the current lldb? > @DavidSpickett, do you have any thoughts on this? :) > For example, on linux, these system logs are normally only readable by root, > so a normal user wouldn't even be able to see what is being logged So if we wanted to implement "here is a log you should send to an lldb developer if they ask for it", then we'd need to log to somewhere else anyway. Certainly if someone is shipping lldb within an organisation they could implement that, but I'm not convinced it's required for Linux right now. And at that point why log to the Darwin system log not some other file? At least it would have a consistent name across platforms then. It sounds like these messages are currently dropped so we could just change Darwin to push to the system log and leave the rest as is and it wouldn't be a regression. Is that correct? That's a way forward at least. (idk if you are aiming to enable this on all platforms for the Swift project's benefit) I'm also curious how useful the system log is if it contains other output. Maybe that's the reason it's useful, if it can tell you about system events that caused the problem, but having random services' output in there seems A: annoying and B: something a issue reporter might be wary of sharing. https://github.com/llvm/llvm-project/pull/111911 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
