Enable kmp-rt for SLERT15 SP6

• Files Changed
• Browse Source

This is a straight import from Factory, it's required to fix build with glibc 2.38 (jsc#PED-7329, bsc#1217126).

Factory never had the following patch, which is not needed anymore:
- crash-ppc64-handle-backtrace-in-emergency-stack.patch (bsc#1210396)

The same change is part of crash upstream since 8.0.2: https://github.com/crash-utility/crash/commit/cdd57e8b16aba2f5714673368d6dbc7565d59841

--------

- Tidy patches to apply without offsets to crash 8.0.4/gdb 10.2:
 - crash-allow-use-of-sadump-captured-KASLR-kernel.patch
 - crash-debuginfo-compressed.patch
 - crash-make-emacs-default.diff
 - crash-sles9-time.patch
 - crash-stop_read_error_when_intent_is_retry.patch
 - crash-usrmerge.patch
- Update to crash-8.0.4
 - Removed patches already present in upstream source:
  * crash-fix-glibc-redefs.patch
  * crash-get-linux_banner-without-using-syment-type.patch
- Removed the redundant clean section from the spec file

- Updated crash gcore extension to current upstream v1.64 dated
  2023-02-28. It's not updated in each product version and most
  don't release a crash-gcore rpm now but updated the latest
  openSUSE package project at this time.

- On initialization crash verifies the core based on the text
  referenced by the linux_banner symbol in the supplied core. It
  chooses how to get the address of the text based on the symbol
  type decoded with gdb. For some compressed kernels with an
  accessible debuginfo file the type is not supported (bss segment
  found, data reference expected) but the symbol and it's value are
  valid. This causes the linux_banner text to be used as the
  "address" of the linux_banner and that's an invalid address for
   the coredump causing crash to fail to load reporting something
  like:
  WARNING: invalid linux_banner pointer: 65762078756e694c
  where the address is obviously ASCII text used as a number. A

• Files Changed
• Browse Source

initialize package

• Browse Source