Jlalond wrote:

> It's crude but maybe just include SI_KERNEL in there? "sent by kernel 
> (SI_KERNEL)". Then we don't have to explain the meaning of SI_KERNEL but I 
> the user do have something I can look up and read about it. And if they do 
> have a kernel side problem, doing some reading is what they'll need to do 
> anyway.

As @labath mentioned there are a lot of things that could cause this. So I 
think the crude approach is the right one! I've updated the patch.

https://github.com/llvm/llvm-project/pull/144800
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to