diff options
| author | Jacob Lalonde <jalalonde@fb.com> | 2025-06-24 09:54:14 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-24 09:54:14 -0700 |
| commit | 353f75410a19328c57a2c91969e239a1f3c33a02 (patch) | |
| tree | 5574b9e8eabd18e0e95080af895b5f0947033647 /llvm/lib/CodeGen/AsmPrinter/CodeViewDebug.cpp | |
| parent | 7377410ddaf2932643849f918ceaff851917f5b5 (diff) | |
| download | llvm-353f75410a19328c57a2c91969e239a1f3c33a02.zip llvm-353f75410a19328c57a2c91969e239a1f3c33a02.tar.gz llvm-353f75410a19328c57a2c91969e239a1f3c33a02.tar.bz2 | |
[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)
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.
Diffstat (limited to 'llvm/lib/CodeGen/AsmPrinter/CodeViewDebug.cpp')
0 files changed, 0 insertions, 0 deletions