[all-commits] [llvm/llvm-project] 353f75: [LLDB] Add SI_USER and SI_KERNEL to Linux signals ...

[Jacob Lalonde via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 353f75410a19328c57a2c91969e239a1f3c33a02
      https://github.com/llvm/llvm-project/commit/353f75410a19328c57a2c91969e239a1f3c33a02
  Author: Jacob Lalonde <jalalonde at fb.com>
  Date:   2025-06-24 (Tue, 24 Jun 2025)

  Changed paths:
    M lldb/source/Plugins/Process/Utility/LinuxSignals.cpp

  Log Message:
  -----------
  [LLDB] Add SI_USER and SI_KERNEL to Linux signals (#144800)

@dmpots and I were investigating a crash when he was developing LLDB
earlier. When I loaded the core I was surprised to see LLDB didn't have
information for the SI_CODE. Upon inspection we had an si_code of `128`,
which is the decimal of SI_KERNEL at `0x80`.

These were overlooked in my last addition of the negative si_codes, and
this patch adds SI_USER and SI_KERNEL to the list, covering us for all
the codes available to all signals.

[Linux reference
link](https://github.com/torvalds/linux/blob/74b4cc9b8780bfe8a3992c9ac0033bf22ac01f19/include/uapi/asm-generic/siginfo.h#L175)


![image](https://github.com/user-attachments/assets/52fa58e6-13d4-48a1-8d82-184c07a47db8)

I kept the code naming the same as what is defined in the Linux source
code. SI_KERNEL to my understanding usually indicates something went
awry in the Kernel itself, but I think adding that additional detail
would not be helpful to most users. @DavidSpickett I'd appreciate your
insight into that.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications