[Lldb-commits] [lldb] [LLDB] Add SI_USER and SI_KERNEL to Linux signals (PR #144800)

David Spickett via lldb-commits lldb-commits at lists.llvm.org
Fri Jun 20 02:26:36 PDT 2025


DavidSpickett wrote:

Depending on the user's knowledge of / interpretation of how signals work, I don't think "sent by kernel" is enough for them to find their specific problem.

Asking my nearest totally accurate AI model:
> Yes, when an application receives a SIGILL (illegal instruction) signal, it is sent by the kernel.

And you can argue this is just the implementation of signals, not the way applications are supposed to think about it, but I think it's one a lot of people would subscribe to.

What you're saying here is that the cause of the generation of the signal (by whomever generates it), was located in a certain place. So the place that tried to execute the illegal instruction,  not the place that wrapped up that exception data into a signal.

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.

https://github.com/llvm/llvm-project/pull/144800


More information about the lldb-commits mailing list