Change log for crash package in Ubuntu

crash (8.0.4-1ubuntu2) noble; urgency=high

  * No change rebuild for 64-bit time_t and frame pointers.

 -- Julian Andres Klode <email address hidden>  Mon, 08 Apr 2024 17:55:38 +0200

Available diffs

• diff from 8.0.4-1ubuntu1 to 8.0.4-1ubuntu2 (353 bytes)

crash (8.0.4-1ubuntu1) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes: (LP: #2047861)
    - d/t/live: If the "live" autopkgtest fails with a recommendation to
      try /proc/kcore instead of the default, attempt that before
      failing the test. LP 1858958.
    - d/t/live: Fix logic issue in "live" autopkgtest introduced in the
      last upload.
    - d/t/live: Fix test, as if will return 0 when no cases were true.
    - d/t/control: Add linux-libc-dev dependency for the autopkg test.
      This package gets usually broken with kernel upgrades, so let it
      already show in the autopkg test.
    - d/t/control: Run autopkg test with allow-stderr.
  * Drop changes:
    - d/p/0002-Fix-compilation-error-due-to-new-strlcpy-function.patch
      [ included upstream in 8.0.4 ]
    - d/p/0003-Support-module-memory-layout-change-on-Linux-6.4.patch
      [ included upstream in 8.0.4 ]

 -- Mauricio Faria de Oliveira <email address hidden>  Tue, 02 Jan 2024 19:09:28 -0300

Available diffs

• diff from 8.0.3+ds1-3ubuntu1 to 8.0.4-1ubuntu1 (51.7 KiB)

crash (8.0.3+ds1-3ubuntu1) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes: (LP: #2042357)
    - d/t/live: If the "live" autopkgtest fails with a recommendation to
      try /proc/kcore instead of the default, attempt that before
      failing the test. LP 1858958.
    - d/t/live: Fix logic issue in "live" autopkgtest introduced in the
      last upload.
    - d/t/live: Fix test, as if will return 0 when no cases were true.
    - d/t/control: Add linux-libc-dev dependency for the autopkg test.
      This package gets usually broken with kernel upgrades, so let it
      already show in the autopkg test.
    - d/t/control: Run autopkg test with allow-stderr.
  * Drop changes:
    - d/rules: Build without lto. Fails to build gdb on ppc64el. That
      should be fixed, once gdb is updated to a more recent version
      (e.g. 10.x). [This line is already commented out since Mantic.]
  * New changes:
    - d/p/0002-Fix-compilation-error-due-to-new-strlcpy-function.patch:
      Fix FTBFS due to strlcpy() introduced in glibc 2.38.
    - d/p/0003-Support-module-memory-layout-change-on-Linux-6.4.patch:
      Fix fatal 'crash: invalid structure member offset: module_core_size'

 -- Mauricio Faria de Oliveira <email address hidden>  Tue, 07 Nov 2023 15:00:36 -0300

Available diffs

• diff from 8.0.2-1ubuntu1 to 8.0.3+ds1-3ubuntu1 (112.1 KiB)

crash (8.0.2-1ubuntu1) mantic; urgency=medium

  * Merge with Debian; remaining changes:
    - Add linux-libc-dev dependency for the autopkg test. This package
      gets usually broken with kernel upgrades, so let it already show
      in the autopkg test.
    - Run autopkg test with allow-stderr.

Available diffs

• diff from 8.0.0-1ubuntu1 to 8.0.2-1ubuntu1 (73.7 KiB)

crash (7.3.0-1ubuntu2) jammy; urgency=medium

  * No-change rebuild for ppc64el baseline bump.

 -- Łukasz 'sil2100' Zemczak <email address hidden>  Wed, 23 Mar 2022 14:48:55 +0100

Available diffs

• diff from 8.0.0-1ubuntu1 (in Ubuntu) to 7.3.0-1ubuntu2 (26.5 MiB)
• diff from 7.3.0-1ubuntu1 (in Ubuntu) to 7.3.0-1ubuntu2 (345 bytes)

crash (8.0.0-1ubuntu1) jammy; urgency=medium

  * Merge with Debian; remaining changes:
    - Build without lto. Fails to build gdb on ppc64el. That should be fixed,
      once gdb is updated to a more recent version (e.g. 10.x).
    - Add linux-libc-dev dependency for the autopkg test. This package
      gets usually broken with kernel upgrades, so let it already show
      in the autopkg test.
  * Run autopkg test with allow-stderr.

Available diffs

• diff from 7.3.0-1ubuntu1 to 8.0.0-1ubuntu1 (26.5 MiB)

crash (7.3.0-1ubuntu1) impish; urgency=medium

  * Merge with Debian; remaining changes:
    - Build without lto. Fails to build gdb on ppc64el. That should be fixed,
      once gdb is updated to a more recent version (e.g. 10.x).
    - Add linux-libc-dev dependency for the autopkg test. This package
      gets usually broken with kernel upgrades, so let it already show
      in the autopkg test.

 -- dann frazier <email address hidden>  Thu, 08 Jul 2021 09:16:21 -0600

Available diffs

• diff from 7.2.9-2ubuntu3 to 7.3.0-1ubuntu1 (56.1 KiB)

crash (7.2.9-2ubuntu3) impish; urgency=medium

  * Add linux-libc-dev dependency for the autopkg test. This package
    gets usually broken with kernel upgrades, so let it already show
    in the autopkg test.

 -- Matthias Klose <email address hidden>  Mon, 21 Jun 2021 09:54:43 +0200

Available diffs

• diff from 7.2.9-2ubuntu2 to 7.2.9-2ubuntu3 (546 bytes)

crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium

  * Fix FTBFS (LP: #1931435):
    - d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch

Available diffs

• diff from 7.2.8-1ubuntu1.20.10.1 to 7.2.8-1ubuntu1.20.10.2 (1.2 KiB)

crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium

  * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275):
    - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch

 -- Ioanna Alifieraki <email address hidden>  Thu, 15 Apr 2021 12:18:59 +0300

Available diffs

• diff from 7.2.8-1ubuntu1 to 7.2.8-1ubuntu1.20.10.1 (1.3 KiB)

crash (7.2.8-1ubuntu1.20.04.1) focal; urgency=medium

  * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275):
    - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch

 -- Ioanna Alifieraki <email address hidden>  Thu, 15 Apr 2021 12:33:46 +0300

Available diffs

• diff from 7.2.8-1ubuntu1 to 7.2.8-1ubuntu1.20.04.1 (1.3 KiB)

crash (7.2.8-1ubuntu0.18.04.2) bionic; urgency=medium

  * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275):
    - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch

 -- Ioanna Alifieraki <email address hidden>  Wed, 14 Apr 2021 18:41:40 +0300

Available diffs

• diff from 7.2.8-1ubuntu0.18.04.1 to 7.2.8-1ubuntu0.18.04.2 (1.4 KiB)

crash (7.2.9-2ubuntu2) hirsute; urgency=medium

  * Build without lto. Fails to build gdb on ppc64el. That should be fixed,
    once gdb is updated to a more recent version (e.g. 10.x).

Available diffs

• diff from 7.2.8-1ubuntu1 to 7.2.9-2ubuntu2 (49.5 KiB)
• diff from 7.2.9-2ubuntu1 to 7.2.9-2ubuntu2 (605 bytes)

crash (7.2.9-2ubuntu1) hirsute; urgency=medium

  * Merge with Debian; remaining changes:

Available diffs

• diff from 7.2.8-1ubuntu1 to 7.2.9-2ubuntu1 (49.2 KiB)

crash (7.2.8-1ubuntu0.18.04.1) bionic; urgency=medium

  * Version bump from Focal, based on upstream release 7.2.8 (LP: #1865041):
    - Multiple fixes up to kernel 5.5-rc1 (e.g., fixes for kmem/timer/log
      commands, for kernels with symbol namespaces and with KASLR enabled).
    - Improve handling of /proc/kcore (live memory) for x86_64 kernels with
      CONFIG_RANDOMIZE_BASE enabled.
    - Fix ARM64 page size handling on kernel 4.4 and before.
    - Improve offset gathering and ELF support on KASLR kernels in S390X.
    - Support xz compressed vmlinux.
    - Fallback to log buffer parsing in case panic task can't be determined
      by normal means in the dumpfile.
  * Remaining changes:
    - Update the maintainer field for Ubuntu.
    - If the "live" autopkgtest fails with a recommendation to try
      /proc/kcore instead of the default, attempt that before failing
      the test. LP: #1858958.
  * Fix test, as if will return 0 when no cases were true.

 -- <email address hidden> (Guilherme G. Piccoli)  Thu, 27 Feb 2020 11:12:51 -0300

Available diffs

• diff from 7.2.1-1ubuntu2 to 7.2.8-1ubuntu0.18.04.1 (153.6 KiB)

crash (7.2.8-1ubuntu0.19.10.1) eoan; urgency=medium

  * Version bump from Focal, based on upstream release 7.2.8 (LP: #1865041):
    - Multiple fixes up to kernel 5.5-rc1 (e.g., fixes for kmem/timer/log
      commands, for kernels with symbol namespaces and with KASLR enabled).
    - Improve handling of /proc/kcore (live memory) for x86_64 kernels with
      CONFIG_RANDOMIZE_BASE enabled.
    - Fix ARM64 page size handling on kernel 4.4 and before.
    - Improve offset gathering and ELF support on KASLR kernels in S390X.
    - Support xz compressed vmlinux.
    - Fallback to log buffer parsing in case panic task can't be determined
      by normal means in the dumpfile.
  * Remaining changes:
    - Update the maintainer field for Ubuntu.
    - If the "live" autopkgtest fails with a recommendation to try
      /proc/kcore instead of the default, attempt that before failing
      the test. LP: #1858958.
  * Fix test, as if will return 0 when no cases were true.

 -- <email address hidden> (Guilherme G. Piccoli)  Thu, 27 Feb 2020 11:12:51 -0300

Available diffs

• diff from 7.2.6-1build1 to 7.2.8-1ubuntu0.19.10.1 (34.0 KiB)

crash (7.2.8-1ubuntu1) focal; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Update the maintainer field for Ubuntu.
    - If the "live" autopkgtest fails with a recommendation to try
      /proc/kcore instead of the default, attempt that before failing
      the test. LP: #1858958.
  * Fix test, as if will return 0 when no cases were true.

Available diffs

• diff from 7.2.6-1ubuntu4 to 7.2.8-1ubuntu1 (39.1 KiB)

crash (7.2.6-1ubuntu4) focal; urgency=medium

  * No-change rebuild with fixed binutils on arm64.

 -- Matthias Klose <email address hidden>  Sat, 08 Feb 2020 10:57:37 +0000

Available diffs

• diff from 7.2.6-1ubuntu3 to 7.2.6-1ubuntu4 (331 bytes)

crash (7.2.6-1ubuntu3) focal; urgency=medium

  * Rebuild with updated binutils, fixing an "illegal insruction" crash
    on arm64. LP: #1859226.
  * Update the maintainer field for Ubuntu.

 -- dann frazier <email address hidden>  Sat, 11 Jan 2020 09:36:27 -0700

Available diffs

• diff from 7.2.6-1build1 to 7.2.6-1ubuntu3 (1.1 KiB)
• diff from 7.2.6-1ubuntu2 to 7.2.6-1ubuntu3 (669 bytes)

crash (7.2.6-1ubuntu2) focal; urgency=medium

  * Fix logic issue in "live" autopkgtest introduced in the last upload.

 -- dann frazier <email address hidden>  Thu, 09 Jan 2020 19:24:17 -0700

Available diffs

• diff from 7.2.6-1ubuntu1 to 7.2.6-1ubuntu2 (692 bytes)

crash (7.2.6-1ubuntu1) focal; urgency=medium

  * If the "live" autopkgtest fails with a recommendation to try
    /proc/kcore instead of the default, attempt that before failing
    the test. LP: #1858958.

 -- dann frazier <email address hidden>  Thu, 09 Jan 2020 14:21:45 -0700

Available diffs

• diff from 7.2.6-1build1 to 7.2.6-1ubuntu1 (584 bytes)

crash (7.2.6-1build1) eoan; urgency=medium

  * No-change upload with strops.h and sys/strops.h removed in glibc.

 -- Matthias Klose <email address hidden>  Thu, 05 Sep 2019 10:47:07 +0000

Available diffs

• diff from 7.2.6-1 (in Debian) to 7.2.6-1build1 (344 bytes)

crash (7.2.6-1) unstable; urgency=medium

  * Two fixes for the Xen hypervisor; the first fixes a bug seen with Xen
    4.11.0 during initialization, which fails with the error message "crash:
    invalid kernel virtual address: <address> type: fill_pcpu_struct",
    followed by "WARNING: cannot fill pcpu_struct" and "crash: cannot read
    cpu_info".  The second fix prevents a segmentation violation associated
    with a crash-7.1.1 commit that addressed the Xen 4.5.0 hypervisor symbol
    name change from "dom0" to "hardware_domain".

  * Fix for Linux 4.20 and later x86_64 kernels which are NOT configured with
    CONFIG_RANDOMIZE_BASE.  Linux 4.20 introduced kernel commit
    d52888aa2753e3063a9d3a0c9f72f94aa9809c15, titled "x86/mm: Move LDT remap
    out of KASLR region on 5-level paging", which modified the 4-level and
    5-level paging PAGE_OFFSET values.  Without this patch, the crash session
    fails during initialization with the error message "crash: read error:
    kernel virtual address: <address>  type: tss_struct ist array".  For
    kernels prior to Linux 4.20.0 which have backports of the kernel commit,
    the kernel's PAGE_OFFSET value must be manually specified via the command
    line option "--machdep page_offset=ffff888000000000" for kernels with
    4-level page tables, or "--machdep page_offset=ff11000000000000" for
    kernels with 5-level paging.  (or alternatively the shorter version "-m
    page_offset=<address>" may be used).  The command line option requirement

  * Fix for the "p" command if the expression contains more than one opening
    parenthesis character and a minus/dash sign.  Without the patch, the
    minus/dash sign will get dropped from the command prior to it being passed
    on to gdb for evaluation, and the command will fail with the message "p:
    gdb request failed: <expression>", where the <expression> string will not

  * Fix for the internal parse_line() utility function to account for embedded
    sets of parentheses, which may be used for expressions that are passed to
    gdb by the "p" command.  Without the patch, expressions containing
    embedded sets of parentheses are broken up into multiple argument tokens
    instead of just one.  The previous commit has been reverted by this one.

  * First phase of support for ARM64 kernels that are configured with
    CONFIG_ARM64_USER_VA_BITS_52, which causes the PTRS_PER_PGD count to
    increase from 64 to 1024.  Without the patch, "WARNING: cannot access
    vmalloc'd module memory" will be displayed during session initialization,
    and the translation of any mapped kernel virtual address that requires a
    page table walk will fail, leading to a myriad of other errors.

  * Support for configurable CONFIG_ARM64_PA_BITS values introduced in kernel
    commit 982aa7c5f0861bf56b2412ca341a13f44c238ba4, titled "arm64: add
    kconfig symbol to configure physical address size".  Without the patch, it
    is impossible to determine the value of CONFIG_ARM64_PA_BITS is, and will
    require a new MAX_PHYSMEM_BITS vmcoreinfo entry to be exported.  This

  * For live system analysis where there is no vmcoreinfo ELF note attached to
    /proc/kcore, or for dumpfile analysis where there is no vmcoreinfo ELF
    note attached to the dumpfile, this patch sets the internal
    pc->read_vmcoreinfo() function to a new plugin function that reads the
    data directly from the live kernel or dumpfile.  Because the function is
    set much later during initialization than if the ELF note is attached to
    /proc/kcore or the dumpfile, it may not be available during very early

  * Fix for Linux 4.14.84 and later 4.14-based x86_64 kernels which are NOT
    configured with CONFIG_RANDOMIZE_BASE and have backported kernel commit
    d52888aa2753e3063a9d3a0c9f72f94aa9809c15, titled "x86/mm: Move LDT remap
    out of KASLR region on 5-level paging", which modified the 4-level and
    5-level paging PAGE_OFFSET values.  Without this patch, the crash session
    fails during initialization with the error message "crash: read error:
    kernel virtual address: <address>  type: tss_struct ist array".

  * Fix for determining the x86_64 "phys_base" value in dumpfiles created by
    the KVM "virsh dump" facility if the kernel is KASLR-enabled and does not
    have the phys_base value stored in vmcoreinfo data.  Without the patch,
    the message "WARNING: cannot determine physical base address: defaulting
    to 0" is displayed, and the crash session fails to initialize.

  * 32-bit ARM kernels built with the Thumb-2 instruction set utilize the R7
    register instead of FP for unwinding stacks using the DWARF unwinder.  On
    those kernels, without the patch, the "bt" command only shows the task

  * Fix for the "kmem -z" option on Linux 5.0 and later kernels that contain
    commit a921444382b49cc7fdeca3fba3e278bc09484a27, titled "mm: move zone
    watermark accesses behind an accessor".  Without the patch, the command
    fails with the error message "kmem: invalid (optional) structure member
    offsets: zone_pages_min or zone_struct_pages_min".

  * Fix for the "kmem -i" option on Linux 5.0 and later kernels that contain
    commit ca79b0c211af63fa3276f0e3fd7dd9ada2439839 titled "mm: convert
    totalram_pages and totalhigh_pages variables to atomic".  Without the
    patch, the command prints some incorrect values, and besides does not
    print high/low memory information on kernels which are configured with

  * Fix for the display of kernel module symbol types by the "sym" command in
    Linux 5.0 and later kernels if the module debuginfo data has not been
    loaded into the crash session.  The st_info member of the Elf32_Sym or
    Elf64_Sym structures has changed so as to not contain ASCII symbol type
    characters, and as a result the "sym" command will show unprintable data
    as the symbol type.  With the patch, only text types ("t" or "T") will be

  * First phase of support of the upcoming ARM64 kernel memory map changes to
    support 52-bit kernel virtual addressing, which allows the configuration
    of CONFIG_ARM64_VA_BITS to be 52, but where the actual number of VA bits
    may be downgraded during boot depending upon the hardware capability.
    This phase is only applicable for live system analysis.

  * Fix for the "dis <function>" option with kernel module text symbols on
    Linux 5.0 and later kernels.  Without the patch, the disassembly may stop
    prematurely or extend into the next function because the st_size member of
    the Elf32_Sym or Elf64_Sym text symbol structures can no longer be used as

  * Commit dd12805ed1db7 in the linux-next kernel repository, titled "XArray:
    Remove radix tree compatibility", changes the definition of
    "radix_tree_root" back to be a struct.  However, the content of the new
    structure differs from the original structure, so without the patch,
    current linux-next kernels fail during initialization with the error
    message "radix trees do not exist or have changed their format".  Because
    the new "radix_tree_root" and "xarray" structures have nearly the same
    layout, the existing functionality for XArrays can be reused.

  * Fixes for the "trace.so" extension module: (1) The reader_page can be
    empty if it was never read, do not record it if it is empty. Better yet,
    do not record any page that is empty.  The struct buffer_page "real_end"
    is not available in older kernels, so it needs to be tested if it exists
    before we can use it.  (2) In newer kernels, the sp->type of kernel module
    symbols does not contain the symbol type character unless the module's
    debuginfo data has been loaded into the crash session.  Writing a garbage
    type to the kallsyms file for trace-cmd to read causes it to crash, so
    just always write an 'm'.  (3) Add the "trace dump -t <trace.dat>" option

  * Fix to find the kernel configuration data in Linux 5.1 kernels containing
    commit 13610aa908dcfce77135bb799c0a10d0172da6ba, titled "kernel/configs:
    use .incbin directive to embed config_data.gz".  Without the patch, new
    kernels configured with CONFIG_IKCONFIG_PROC will display "WARNING: could
    not find MAGIC_START!" during session initialization, and also when

  * Fix for the PPC64 "bt" command running against kernels that are configured
    with CONFIG_THREAD_INFO_IN_TASK.  Without the patch, the "bt" command
    fails with the message "bt: invalid/stale stack pointer for this task:

  * Fix for the "files -d <dentry>" option if the dentry.d_inode pointer is
    NULL.  Without the patch, the command output does not display the

  * When the is_s390_dump() function is called to determine whether a file is
    an s390 dumpfile, it currently presumes that the fopen() call always
    works, and then tries to read it with using a NULL file pointer.  Change
    it to verify that the fopen() was successful, and if not, print an error
    message as is done with the other dumpfile type verifier functions.

  * Implement support for ARM64 kernels that are configured with:
    CONFIG_ARM64_PA_BITS=52 CONFIG_ARM64_64K_PAGES CONFIG_PGTABLE_LEVELS=3 and
    that run on a host containing physical memory that utilizes any bit in the
    uppermost 4 bits of the 52-bit physical address range.

  * Extension of the "snap.so" extension module to pass a second
    architecture-specific value in the ELF header; its initial use is for
    support of the upcoming ARM64 52-bit kernel virtual address space by

  * Apply initial changes to support kernel address space layout randomization
    (KASLR) for s390X.  This is the minimal patch-set required to process
    s390x dumps for the kernels configured with CONFIG_RANDOMIZE_BASE, and to
    accept the "--kaslr" command line option.  Only dumpfiles whose headers

  * Fix for the "dev -[dD]" options on Linux 5.1-rc1 and later kernels that
    contain commit 570d0200123fb4f809aa2f6226e93a458d664d70, titled "driver
    core: move device->knode_class to device_private".  Without the patch, the
    command options fail with the error message "dev: invalid structure member

  * Linux 4.18 kernels introduced a new CONFIG_PROC_VMCORE_DEVICE_DUMP
    configuration in commit 2724273e8fd00b512596a77ee063f49b25f36507, titled
    "vmcore: add API to collect hardware dump in second kernel", in which
    device drivers may collect a device specific snapshot of the
    hardware/firmware state of their underlying devices, and export the data
    as a kdump ELF note with type NT_VMCOREDD.  This patch recognizes the new
    ELF note(s) in both ELF and compressed kdump vmcore dumpfiles.  The "help
    -[nD]" option shows basic information about each note, and two new "dev"
    command options have been introduced.  The "dev -V" option displays an
    indexed list of each note, showing the device name, the dumpfile offset,
    and the size of each note.  The "dev -v index [file]" option either dumps
    the contents of a note to the display screen in a human-readable format,
    or copies the note data directly to a specified file.

  * If the kernel's "vmap_area_list" doubly-linked list is corrupt such that
    it does not link back to the global list_head, commands that require
    information regarding the range of virtually-mapped kernel addresses will
    display a generic list-handling error message such as "kmem: invalid list
    entry: 0", and the command will typically fail to fully complete.
    However, without the patch, there will also be "WARNING: malloc/free
    mismatch (29/30)" messages that get displayed after every subsequent
    command.  This patch prevents the mismatch messages, and also adds an
    additional error message indicating "WARNING: invalid/corrupt
    vmap_area_list" to further clarify the generic list-handling error

  * Fix for the "dev" help page to remove the unused -r option letter.

  * If a duplicate list entry is encountered when using the "list -B" Brent
    algorithm, change the list loop length value from hexadecimal to decimal.

  * Update the README file to indicate the capability of building an x86_64
    crash binary with "make target=PPC64", which can be used to analyze

  * Fix for hybrid kernels that have backported support for the Xarray
    facility while allowing subsystems to continue to use radix trees.
    Without the patch, the crash session fails during initialization with the
    message "crash: xarray facility does not exist or has changed its format".

 -- Troy Heber <email address hidden>  Mon, 15 Jul 2019 08:20:49 -0600

Available diffs

• diff from 7.2.5-1 to 7.2.6-1 (26.2 KiB)

crash (7.2.1-1ubuntu2) bionic; urgency=medium

  * Add patch to fix ipcs command (LP: #1765660).
  * Add test for ipcs command.

 -- Thadeu Lima de Souza Cascardo <email address hidden>  Fri, 15 Feb 2019 06:58:17 -0200

Available diffs

• diff from 7.2.1-1 (in Debian) to 7.2.1-1ubuntu2 (2.7 KiB)

crash (7.2.5-1) unstable; urgency=medium

  * New upstream (Closes: #919291)

  * Resurrection of the "dev -p" option for displaying PCI device data on
    Linux 2.6.26 and later kernels.  The option was deprecated as of Linux
    2.6.26, and without the patch, the option would indicate "dev: -p option
    not supported or applicable on this architecture or kernel" when running
    against the newer kernel versions.  PCI Bus information will also be
    displayed with this patch.

  * With Linux 4.19-rc1 commit 7d4340bb92a9df78e6e28152f3dd89d9bd82146b,
    titled "powerpc/mm: Increase MAX_PHYSMEM_BITS to 128TB with
    SPARSEMEM_VMEMMAP config", the PPC64 MAX_PHYSMEM_BITS value has been
    bumped up to 47.  The appropriate update has been made in this patch.

  * Fix to allow piping command output to a shell script beginning with a
    shebang (#!) character sequence if the script pathname is specified with a
    preceding "./" or "/".  Without the patch, the piped command fails with
    the message "crash: pipe operation failed".

  * Fix for the PPC64 "bt" command to recognize when a thread is running in
    OPAL firmware.  Without the patch, the "bt" command indicates
    <task-address>: Invalid Stack Pointer <OPAL-firmware-address>"

  * As an addendum to the "dev -p" patch above, add the new structure member
    offsets for display by the "help -o" option.

  * Enhancement to the "kmem -n" option to dump memory block information if
    the kernel supports it.  In addition, the memory section data block has a
    new "STATE" column added to it.

  * Addendum to the previous "kmem -n" patch to fix a FTBFS issue.   Without
    the patch, certain architectures fail to compile with the error
    "memory.c:17315:16: error: ‘PAGE_SHIFT’ undeclared (first use in this
    function)"

  * Fix the calculation of the vmalloc memory region size to account for Linux
    4.17 commit a7412546d8cb5ad578805060b4006f2a021b5868, titled "x86/mm:
    Adjust vmalloc base and size at boot-time", which increases the region's
    size from 32TB to 1280TB when 5-level pagetables are enabled.  Also
    presume that virtual addresses above the end of the vmalloc space up to
    the beginning of vmemmap space are translatable via 5-level page tables.
    Without the patch, mapped virtual addresses may fail translation in
    whatever command accesses them, with errors indicating "seek error: kernel
    virtual address: <mapped-address>  type: <type-string>"

  * Address several Coverity Scan "RESOURCE_LEAK" issues in the following
    top-level source files: cmdline.c, kvmdump.c, lkcd_v8.c, xendump.c,
    symbols.c, unwind_x86_32_64.c, va_server.c and va_server_v1.c.

  * Modify the x86_64 "bt" behavior when a legitimate exception RIP value
    cannot be referenced symbolically, such as when the exception occurs while
    running in seccomp BPF filter code.  Without the patch, the exception
    frame register dump is preceded by "[exception RIP: unknown or invalid
    address]", and then followed by "bt: WARNING: possibly bogus exception
    frame".  With the patch applied, the translation of the exception RIP will
    show "[exception RIP: no symbolic reference]", and there will be no
    warning message.

  * Account for the /proc/kcore VMCOREINFO PT_NOTE in Linux 4.19 and later
    kernels having commit 23c85094fe1895caefdd19ef624ee687ec5f4507, titled
    "proc/kcore: add vmcoreinfo note to /proc/kcore".  The PT_NOTE information
    is stored during session initialization for later display by "help
    -[n|D]"; a subsequent commit will make it available for use by the crash
    utility's internal pc->read_vmcoreinfo() function.

  * Second phase of support for the VMCOREINFO PT_NOTE added to the ELF header
    of /proc/kcore in Linux 4.19 and later kernels.  This patch introduces
    support for live session /proc/kcore VMCOREINFO access by the crash
    utility's internal pc->read_vmcoreinfo() function.  New usage include the
    initialization of the x86_64 phys_base value, and the arm64 phys_offset,
    page size, and VA bits count.

  * Fix for Linux 4.20-rc1 and later kernels that contain kernel commit
    5c83511bdb9832c86be20fb86b783356e2f58062, titled "x86/paravirt: Use a
    single ops structure".  Without the patch, the kernel may be misidentified
    as an ARCH_XEN kernel, with the most noticeable result being the inability
    to read vmemmap'd page structures.

  * Implemented the functionality for a new MEMBER_TYPE_NAME() macro, which
    will return a pointer to the type name string of a structure member.  It
    is being put in place for the support of Linux 4.20 radix tree to xarray
    replacements, where structure member types may be changed from
    radix_tree_root structures to xarray structures.

  * First phase of support for the XArray facility.  The added support is
    similar to that of radix trees, but introduces completely separate
    functions, structures and #defines.  None of the applicable radix tree
    users in the crash utility have been switched over, so this phase does not
    introduce any functional changes.

  * Second phase of support for the XArray facility, which handles the
    switch-over of PID handling from a radix tree to an XArray in Linux 4.20
    and later kernels.  Without the patch, the crash session fails during
    session initialization with the message "crash: radix trees do not exist
    or have changed their format".

  * Third phase of support for the XArray facility, which consolidates the
    radix_tree_pair and xarray_pair structures into a unified list_pair
    structure that is used by both facilities, and fixes the "bpf" command.
    Without the patch, the command fails on Linux 4.20 or later kernels with
    the error message "bpf: radix trees do not exist or have changed their
    format".

  * Added support for usage of the XArray facility by the "files -p" option.
    Without the patch, the command fails on Linux 4.20 and later kernels with
    the error message "files: radix trees do not exist or have changed their
    format".

  * Added support for usage of the XArray facility by the "irq" command.
    Without the patch, the command fails on Linux 4.20 and later kernels with
    the error message "irq: radix trees do not exist or have changed their
    format".

  * Added support for usage of the XArray facility by the "ipcs" command.
    Without the patch, the command may fail on Linux 4.20 and later kernels
    with the error message "irq: radix trees do not exist or have changed
    their format".

  * Added a new "tree -t xarray" option to display of the contents of an
    XArray in Linux 4.20 and later kernels.  The implementation is similar to
    that of radix tree displays, but in addition, the "-p" option will also
    display the index value of each entry in a radix tree or XArray.

  * Fix for the "files -p <inode>" option on a file with a large number of
    pages.  Without the patch, the command attempts to read radix tree node
    slot entries that are RADIX_TREE_EXCEPTIONAL_ENTRY types instead of page
    pointers, and as a result may fail with a dump of the internal buffer
    allocation stats followed by the message "files: cannot allocate any more
    memory!".

  * Fix for the "ps -s" option on ARM64 if the number of tasks exceeds 2000.
    Without the patch, the command ultimately fails with a dump of the
    internal buffer allocation stats, followed by the message "ps: cannot
    allocate any more memory!".

  * With Linux 4.20-rc1 commit 4ffe713b7587b14695c9bec26a000fc88ef54895,
    titled "powerpc/mm: Increase the max addressable memory to 2PB", the PPC64
    MAX_PHYSMEM_BITS value has been bumped up to 51 for
    CONFIG_SPARSEMEM_VMEMMAP and CONFIG_SPARSEMEM_EXTREME.  The appropriate
    update has been made in this patch.

  * Implemented a new plugin function for the readline library's tab
    completion feature.  Without the patch, the use of the default plugin from
    the embedded gdb module has been seen to cause segmentation violations or
    other fatal malloc/free/corruption assertions.  The new plugin takes gdb
    out of the picture entirely, and also restricts the matching options to
    just symbol names, so as not to clutter the results with irrelevant
    filenames.

  * The RHEL8 kernel will contain a backport of the Linux 4.19 kernel commit
    7d4340bb92a9df78e6e28152f3dd89d9bd82146b, titled "powerpc/mm: Increase
    MAX_PHYSMEM_BITS to 128TB with SPARSEMEM_VMEMMAP config".  As a result,
    the use of the THIS_KERNEL_VERSION() macro by the crash utility does not
    suffice for determining the MAX_PHYSMEM_BITS value for PPC64.  The
    appropriate update has been made in this patch.

  * Fix for an initialization-time session failure when all three of the
    following conditions exist: (1) invoking the session with "crash -d2" or
    larger debug number (2) running against a Linux 3.3 or later kernel (3)
    using a post-7.2.4 crash utility that has the new "kmem -n" support above
    for the display of memory blocks Without the patch, the crash session
    fails with the error message "crash: invalid structure member offset:
    device_kobj".

  * Fix for an initialization-time segmentation violation when invoking
    crash-7.2.4 or later with "crash -d2" or larger debug number.

  * Add a write operation handler to the sample /dev/crash memory driver that
    enables writing to kernel memory via the "wr" command.

  * Prevent a SIGSEGV if a user attempts to input a command line that exceeds
    the maximum length of 1500 bytes.  The patch displays an error message and
    ignores the command line.

  * Fix for the "dev -[dD]" options in kernels containing Linux 5.0-rc1 commit
    7ff4f8035695984c513598e2d49c8277d5d234ca, titled "block: remove dead queue
    members", in which the number of I/Os issued to a disk driver are no
    longer stored in the request_queue structure.  Without the patch, the
    options indicate "dev: -d option not supported or applicable on this
    architecture or kernel".  With the patch, the "DRV" column is not shown.

  * A crash-7.1.1 commit added support for Linux version 5.x.  To prevent
    surprise failures due to unexpected kernel version bumps in the future,
    support has been added for version 6, keeping it one step ahead.

  * Fix for a gcc-9 compilation error that occurs if an inline asm statement
    clobbers the stack pointer.  Without the patch, x86 and x86_64 builds will
    fail to compile gdb-7.6/gdb/common/linux-ptrace.c, generating an error
    that indicates "error: Stack Pointer register clobbered by '%rsp' in
    'asm'".

 -- Troy Heber <email address hidden>  Tue, 29 Jan 2019 08:55:24 -0700

Available diffs

• diff from 7.2.3+real-2 to 7.2.5-1 (65.2 KiB)

crash (7.2.3+real-2) unstable; urgency=medium

  * Patch from Helmut Grohne <email address hidden> to support non-glibc libcs
    (Closes: #910235)

 -- Troy Heber <email address hidden>  Thu, 11 Oct 2018 09:47:22 -0600

Available diffs

• diff from 7.2.3+real-1 to 7.2.3+real-2 (863 bytes)

crash (7.2.3+real-1~16.04.1) xenial; urgency=medium

  * Backport to xenial. LP: #1746088
    - Build-Depends on debhelper 9.

 -- Thadeu Lima de Souza Cascardo <email address hidden>  Tue, 26 Jun 2018 14:32:30 -0300

Available diffs

• diff from 7.1.4-1ubuntu4.2 (in ~canonical-kernel-team/ubuntu/azure) to 7.2.3+real-1~16.04.1 (256.0 KiB)

crash (7.2.3+real-1) unstable; urgency=medium

  * Revert wget addition and re-include embedded gdb (Closes: #901863)

 -- Troy Heber <email address hidden>  Fri, 22 Jun 2018 15:39:16 -0600

Available diffs

• diff from 7.2.1-1ubuntu1 (in Ubuntu) to 7.2.3+real-1 (59.9 KiB)
• diff from 7.2.3-2 to 7.2.3+real-1 (28.6 MiB)

crash (7.2.3-2) unstable; urgency=medium

  * Add wget as a builddep

 -- Troy Heber <email address hidden>  Tue, 22 May 2018 09:16:03 -0600

Available diffs

• diff from 7.2.3-1 to 7.2.3-2 (528 bytes)

crash (7.2.3-1) unstable; urgency=medium

  * Fix for a crash-7.2.2 regression that may cause the "mount" command to
    generate a segmentation violation.  The bug is dependent upon the compiler
    version used to build the crash utility, where a buffer overrun is not
    seen with more recent versions of gcc, which hide the bug due to a
    different stack layout of a function's local variables.

  * Fix for a second crash-7.2.2 buffer overrun regression that may cause the
    "rd -S" option to generate a segmentation violation if a displayed memory
    location contains a slab object address.

  * Fix for a third, highly unlikely, crash-7.2.2 buffer overrun regression,
    that could potentially occur during session initialization.

 -- Troy Heber <email address hidden>  Mon, 21 May 2018 14:01:30 -0600

Available diffs

• diff from 7.2.1-1ubuntu1 (in Ubuntu) to 7.2.3-1 (28.7 MiB)

crash (7.2.1-1ubuntu1) cosmic; urgency=medium

  * Add patch to fix ipcs command (LP: #1765660).

 -- Thadeu Lima de Souza Cascardo <email address hidden>  Mon, 14 May 2018 16:05:51 -0300

Available diffs

• diff from 7.2.1-1build1 to 7.2.1-1ubuntu1 (2.6 KiB)

crash (7.2.1-1build1) cosmic; urgency=medium

  * No-change rebuild for ncurses soname changes.

 -- Matthias Klose <email address hidden>  Thu, 03 May 2018 14:14:14 +0000

Available diffs

• diff from 7.2.1-1 (in Debian) to 7.2.1-1build1 (308 bytes)

crash (7.2.1-1) unstable; urgency=medium

  * New upstream (closes: #890394)

  * Fix for the "runq" command on Linux 4.14 and later kernels that contain
    commit cd9e61ed1eebbcd5dfad59475d41ec58d9b64b6a, titled "rbtree: cache
    leftmost node internally".  Without the patch, the command fails with the
    error message "runq: invalid structure member offset: cfs_rq_rb_leftmost".

  * Fix to prevent a useless message during session inialization.  Without the
    patch, if the highest possible node bit in the node_states[N_ONLINE]
    multi-word bitmask is set, then a message such as "crash:
    next_online_node: 256 is too large!" will be displayed.

  * Additional fixes for the ARM64 "bt" command for Linux 4.14 kernels.  The
    patch corrects the contents of in-kernel exception frame register dumps,
    and properly transitions the backtrace from the IRQ stack to the process
    stack.

  * Implemented a new "search -T" option, which is identical to the "search
    -t" option, except that the search is restricted to the kernel stacks of
    active tasks.

  * Removal of the ARM64 "bt -o" option for Linux 4.14 and later kernels,
    along with several cleanups/readability improvements.

  * Fix for support of KASLR enabled kernels captured by the SADUMP dumpfile
    facility. SADUMP dumpfile headers do not contain phys_base or VMCOREINFO
    notes, so without this patch, the crash session fails during
    initialization with the message "crash: seek error: kernel virtual
    address: <address>  type: "page_offset_base".  This patch calculates the
    phys_base value and the KASLR offset using the IDTR and CR3 registers from
    the dumpfile header.

  * Implemented a new "ps -y policy" option to filter the task display by
    scheduling policy.  Applicable to both standalone ps invocation as well as
    via foreach.

  * Fix for the "kmem -[sS]" options on Linux 4.14 and later kernels that
    contain commit 2482ddec670fb83717d129012bc558777cb159f7, titled "mm: add
    SLUB free list pointer obfuscation".  Without the patch, there will
    numerous error messages of the type "kmem: <cache name> slab: <address>
    invalid freepointer: <obfuscated address>" if the kernel is configured
    with CONFIG_SLAB_FREELIST_HARDENED.

  * Fix for the validation of the bits located in the least significant bits of
    mem_section.section_mem_map pointers.  Without the patch, the validation
    functions always returned valid, due to a coding error found by clang.
    However, it was never really a problem because it is extremely unlikely
    that an existing mem_section would ever be invalid.

  * Fix for the x86_64 kernel virtual address to physical address translation
    mechanism.  Without the patch, when verifying that the PAGE_PRESENT bit is
    set in the top-level page table, it would always test positively, and the
    translation would continue parsing the remainder of the page tables.  This
    would virtually never be a problem in practice because if the top-level
    page table entry existed, its PAGE_PRESENT bit would be set.

  * Removed a check for a negative block_size value which is always a
    non-negative unsigned value in the SADUMP header parsing function.

  * Removed a check for an impossible negative value when calculating the
    beginning address when applying the context value specified by the "search
    -x <count>" option.

  * Implemented a new "timer -C <cpu-specifier>" option that restricts the
    timer or hrtimer output to the timer queue data associated with one or
    more cpus.  For multiple cpus, the cpu-specifier uses the standard comma
    or dash separated list format.

  * Fix for a "ps -l" regression introduced by the new "ps -y" option
    introduced above.  Without the patch, the -l option generates a
    segmentation violation if not accompanied by a -C cpu specifier option.

  * Fix for the "kmem -i" and "kmem -V" options in Linux 4.8 and later kernels
    containing commit 75ef7184053989118d3814c558a9af62e7376a58, titled "mm,
    vmstat: add infrastructure for per-node vmstats".  Without the patch, the
    CACHED line of "kmem -i" shows 0, and the VM_STAT section of "kmem -V" is
    missing entirely.

  * Fix for Linux 4.11 and later kernels that contain kernel commit
    4b3ef9daa4fc0bba742a79faecb17fdaaead083b, titled "mm/swap: split swap
    cache into 64MB trunks".  Without the patch, the CACHED line of "kmem -i"
    may show nonsensical data.

  * Implemented a new "dev -D" option that is the same as "dev -d", but
    filters out the display of disks that have no I/O in progress.

  * If a line number request for a module text address initially fails, force
    the embedded gdb module to complete its two-stage strategy used for
    reading debuginfo symbol tables from module object files, and then retry
    the line number extraction.  This automatically does what the "mod -r" or
    "crash --readnow" options accomplish.

  * Update for support of Linux 4.12 and later PPC64 kernels where the hash
    page table geometry accommodates a larger virtual address range.  Without
    the patch, the virtual-to-physical translation of user space virtual
    addresses by "vm -p", "vtop", and "rd -u" may generate an invalid
    translation or otherwise fail.

  * Implemented a new "runq -T" option that displays the time lag of each CPU
    relative to the most recent runqueue timestamp.

  * Fix to support Linux 4.15 and later kernels that contain kernel commit
    e8cfbc245e24887e3c30235f71e9e9405e0cfc39, titled "pid: remove pidhash".
    The kernel's traditional usage of a pid_hash[] array to store PIDs has
    been replaced by an IDR radix tree, requiring a new crash plug-in function
    to gather the system's task set.  Without the patch, the crash session
    fails during initialization with the error message "crash: cannot resolve
    init_task_union".

  * Fix for the "net" command when the network device listing has an unusually
    large number of IP addresses.  In that case, without the patch, the
    command may generate a segmentation violation.

  * Fix for Linux 4.15 and later kernels that are configured with
    CONFIG_SPARSEMEM_EXTREME, and that contain kernel commit
    83e3c48729d9ebb7af5a31a504f3fd6aff0348c4, titled "mm/sparsemem: Allocate
    mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y".  Without the
    patch, kernels configured with SPARSEMEM_EXTREME have changed the data
    type of "mem_section" from an array to a pointer, leading to errors in
    commands such as "kmem -p", "kmem -n", "kmem -s", and any other command
    that translates a physical address to its page struct address.

  * With the latest PPC64 NMI IPI changes, crash_ipi_callback is found
    multiple times on the stack of active non-panic tasks.  Ensure that the
    symbol reference relates to an actual backtrace stack frame.

  * Update the starting virtual address of vmalloc space for kernels
    configured with CONFIG_X86_5LEVEL.

  * Update the X86_64 VSYSCALL_END address to reflect that it only contains 1
    page.

  * Prevent the X86_64 FILL_PML() macro from updating the internal
    machdep->machspec->last_pml4_read address every time a vmalloc'd kernel
    virtual address is translated.

  * Fix for the "bt" command in x86_64 kernels that contain, or have backports
    of, kernel commit 4950d6d48a0c43cc61d0bbb76fb10e0214b79c66, titled
    "x86/dumpstack: Remove 64-byte gap at end of irq stack".  Without the
    patch, backtraces fail to transition from the IRQ stack back to the
    process stack, showing an error message such as "bt: cannot transition
    exception stack to IRQ stack to current process stack".

  * Initial pass for support of kernel page table isolation.  The x86_64 "bt"
    command may indicate "bt: cannot transition from exception stack to
    current process stack" if the crash callback NMI occurred while an active
    task was running on the new entry trampoline stack.  This has only been
    tested on the RHEL7 backport of the upstream patch because as of this
    commit, crash does not run on 4.15-rc kernels.  Further changes may be
    required for upstream kernels, and distributions that implement the kernel
    changes differently than upstream.

  * Fix for the "bt" command and the "ps -s" option for zombie tasks whose
    kernel stacks have been freed/detached.  Without the patch, the "bt"
    command indicates "bt: invalid kernel virtual address: 0 type: stack
    contents" and "bt: read of stack at 0 failed"; it will be changed to
    display "(no stack)".  The "ps -s" option would fail prematurely upon
    reaching such a task, indicating "ps: invalid kernel virtual address: 0
    type: stack contents" and "ps: read of stack at 0 failed".

  * Fix for running on live systems on 4.15-rc2 and later kernels that are
    configured with CONFIG_RANDOMIZE_BASE and contain kernel commit
    668533dc0764b30c9dd2baf3ca800156f688326b, titled "kallsyms: take advantage
    of the new '%px' format".  Without the patch, a live crash session does
    not show the "WARNING: kernel relocated ..." message expected with KASLR,
    and then displays the message "crash: cannot set context for pid: <pid>"
    prior to generating a SIGSEGV.

  * Fix for 4.15-rc5 and later x86_64 kernels that contain kernel commit
    c482feefe1aeb150156248ba0fd3e029bc886605, titled "x86/entry/64: Make
    cpu_entry_area.tss read-only".  Without the patch, the addresses and sizes
    of the x86_64 exception stacks cannot be determined; therefore if a
    backtrace starts on one of the exception stacks, then the "bt" command
    will fail.

  * Additional fix for support of KASLR enabled kernels captured by the SADUMP
    dumpfile facility, where this patch fixes a problem when Page Table
    Isolation(PTI) is enabled.  When PTI is enabled, bit 12 of CR3 register is
    used to split user space and kernel space.  Also bit 11:0 is used for
    Process Context IDentifiers(PCID).  To open an SADUMP dumpfile, the value
    of CR3 is used to calculate KASLR offset and phys_base; this patch masks
    the CR3 register value correctly for a PTI enabled kernel.

  * Second phase of future support for x86_64 5-level page tables.  This patch
    is a cleanup/collaboration of the original logic used by the various vtop
    functions, where several new common functions have been added for
    extracting page table entries from PGD, P4D, PUD, PMD and PTE pages.  The
    usage of the former PML4 and UPML pages have been replaced with the use of
    the common PGD page, and use the PUD page in 4-level page table
    translation.  Support for 5-level page tables has been incorporated into
    the the existing x86_64_kvtop() and x86_64_uvtop_level4() functions.
    Backwards compatibility for older legacy kernels has been maintained.  The
    third phase of support will automatically detect whether the kernel
    proper, and whether an individual user task, is utilizing 5-level page
    tables.  This patch enables support for kernel-only 5-level page tables by
    entering the command line option "--machdep vm=5level".

  * Xen commit 615588563e99a23aaf37037c3fee0c413b051f4d (Xen 4.0.0.) extended
    the direct mapping to 5 TB.  This area was previously reserved for future
    use, so it is OK to simply change the upper bound unconditionally.

  * Add a new "foreach gleader" qualifier option, restricting the output to
    user-space tasks that are thread group leaders.

  * Since Xen commit 666aca08175b ("sched: use the auto-generated list of
    schedulers") crash cannot open Xen vmcores because the "schedulers" symbol
    no longer exists.  Xen 4.7 implemented schedulers as its own section in
    "xen/arch/x86/xen.lds.S", delimited by the two symbols
    "__start_schedulers_array" and "__end_schedulers_array".  Without the
    patch, the crash session fails during initialization with the error
    message "crash: cannot resolve schedulers"

  * Fix the sample crash.ko memory driver to prevent an s390X kernel
    addressing exception.  Legitimate pages of RAM that successfully pass the
    page_is_ram() and pfn_valid() verifier functions may not be provided by
    the s390x hypervisor, and the memcpy() from the non-existent memory to the
    bounce buffer panics the kernel.  The patch replaces the the memcpy() call
    with probe_kernel_read().

  * Fix for the ARM64 "bt" command running against Linux 4.14 and later
    kernels.  Without the patch, the backtraces of the active tasks in a
    kdump-generated dumpfile are truncated.  Without the patch, the panic task
    will just show the "crash_kexec" frame and the kernel-entry user-space
    exception frame; the non-panic tasks will show their backtraces starting
    from the stackframe addresses captured in the per-cpu NT_PRSTATUS notes,
    and will not display the exception frame generated by the NMI callback,
    nor any stackframes on the IRQ stack.

  * Fix for the ARM64 "bt" command in kernels that contain commit
    30d88c0e3ace625a92eead9ca0ad94093a8f59fe, titled "arm64: entry: Apply BP
    hardening for suspicious interrupts from EL0".  Without the patch, there
    may be invalid kernel kernel exception frames displayed on an active
    task's kernel stack, often below a stackframe of the
    "do_el0_ia_bp_hardening" function; the address translation of the PC and
    LR values in the the bogus exception frame will display "[unknown or
    invalid address]".

 -- Troy Heber <email address hidden>  Fri, 16 Feb 2018 10:47:33 -0700

Available diffs

• diff from 7.2.0-1 to 7.2.1-1 (44.1 KiB)

crash (7.2.0-1) unstable; urgency=medium

  * New upstream (closes: #884464)

  * Fix for the "snap.so" extension module to pass the KASLR relocation offset
    value in the ELF header for x86_64 kernels that are compiled with
    CONFIG_RANDOMIZE_BASE.  Without the patch, it is necessary to use the
    "--kaslr=<offset>" command line option, or the session fails with the
    message "WARNING: cannot read linux_banner string", followed by "crash:
    vmlinux and vmcore do not match!".

  * The native gdb "disassemble" command fails if the kernel has been compiled
    with CONFIG_RANDOMIZE_BASE because the embedded gdb module still operates
    under the assumption that the (non-relocated) text locations in the
    vmlinux file are correct.  The error message that is issued is somewhat
    confusing, indicating "No function contains specified address".  This
    patch simply clarifies the error message to indicate "crash: the gdb
    "disassemble" command is prohibited because the kernel text was relocated
    by KASLR; use the crash "dis" command instead."

  * Fix for the "mach -m" command in Linux 4.9 and later kernels that contain
    commit 475339684ef19e46f4702e2d185a869a5c454688, titled "x86/e820: Prepare
    e280 code for switch to dynamic storage", in which the "e820" symbol was
    changed from a static e820map structure to a pointer to an e820map
    structure.  Without the patch, the command either displays just the
    header, or the header with several nonsensical entries.

  * Fix for Linux 4.10 and later kdump dumpfiles, or kernels that have
    backported commit 401721ecd1dcb0a428aa5d6832ee05ffbdbffbbe, titled "kexec:
    export the value of phys_base instead of symbol address".  Without the
    patch, if the x86_64 "phys_base" value in the VMCOREINFO note is a
    negative decimal number, the crash session fails during session
    intialization with a "page excluded" or "seek error" when reading
    "page_offset_base".

  * Fix for the PPC64 "pte" command.  Without the patch, if the target PTE
    references a present page, the physical address is incorrect.

  * Fix for a 32-bit MIPS compilation error if glibc-2.25 or later has been
    installed on the host build machine.  Without the patch, the build fails
    with the error message "mips-linux-nat.c:157:1: error: conflicting types
    for 'ps_get_thread_area'".

  * Fix for the validity check of S390X virtual addresses for 5-level page
    tables where user space memory is mapped above 8 Petabytes.  Without the
    patch, "rd -u" fails and indicates "invalid user virtual address", and
    "vtop -u" indicates that the address is "(not mapped)".

  * Crash 7.1.5 commit c3413456599161cabc4e910a0ae91dfe5eec3c21 (xen: Add
    support for dom0 with Linux kernel 3.19 and newer) from Daniel Kiper
    implemented support for Xen dom0 vmcores after Linux 3.19 kernel commit
    054954eb051f35e74b75a566a96fe756015352c8 (xen: switch to linear virtual
    mapped sparse p2m list).  This patch can be deemed subsequent to Daniel's
    patch, and implements support Xen PV domU dumpfiles for Linux 3.19 and
    later kernels.

  * Fix for the "dis" command to detect duplicate symbols in the case of a
    "symbol+offset" argument where the duplicates are not contiguous in the
    symbol list.  Without the patch, the first of multiple symbol instances is
    used in the address evaluation.  With the patch, the command will fail
    with the error message "dis: <symbol+offset>: duplicate text symbols
    found:", followed by a list of the duplicate symbols, and their file and
    line numbers if available.

  * Enhancement to the error reporting mechanism for the "kmem -[sS]" options.
    When a fatal error is encountered while gathering basic CONFIG_SLUB
    statistics, it is possible that the slab cache name is not displayed in
    the error message, and the line containing the slab cache name, address,
    etc., is not displayed at all.  With this patch, an extra error message
    indicating "kmem: <cache-name>: cannot gather relevant slab data" will be
    displayed under the fatal error message; and under that, the CACHE
    address, cache NAME, OBJSIZE, and SSIZE columns will be displayed, but
    with "?" under the ALLOCATED, TOTAL, and SLABS columns.

  * Fix to prevent the "tree -t radix" option from failing when it encounters
    duplicate entries in a radix_tree_node[slots] array.  Without the patch,
    if a duplicate slot entry is found, the command fails with the message
    "tree: duplicate tree entry: radix_tree_node: <node address>
    slots[<index>]: <entry>\n".  (The error can be prevented if the command is
    preceded by "set hash off".)  However, certain radix trees contain
    duplicate entries by design, such as the "pgmap_radix" radix tree, in
    which a radix_tree_node may contain multiple instances of the same
    page_map structure.  With the patch, checks will only be made for
    duplicate radix_tree_node structures.

  * First phase of future support for x86_64 5-level page tables.  New sets of
    virtual memory offsets have been #define'd and helper macros and
    placeholder functions for the p4d page tables have been added.  The only
    functional changes with this patchset are dynamically-set PGDIR_SHIFT and
    PHYSICAL_MASK_SHIFT values that are based upon the kernel configuration.

  * Fix for a build failure.  Without the patch, if the build is done by a
    user whose username cannot be determined from the user ID number, the
    build fails immediately with a segmentation fault.

  * Fix for Linux 4.13-rc0 commit 7fd8329ba502ef76dd91db561c7aed696b2c7720
    "x86/boot/64: Rename init_level4_pgt and early_level4_pgt".  Without the
    patch, the crash session fails during initialization with the error
    message "crash: cannot resolve "init_level4_pgt".

  * The internal "build_data" string contains the compile-time date, the user
    id of the builder, and the build machine hostname, and is viewable by the
    "crash --buildinfo" command line option or by the "help -B" option during
    runtime.  This patch replaces that string data with "reproducible build"
    if the SOURCE_DATE_EPOCH environment variable contains a value string when
    the crash binary is compiled.

  * Fix for Linux 4.13-rc1 commit 2d070eab2e8270c8a84d480bb91e4f739315f03d
    "mm: consider zone which is not fully populated to have holes".  Without
    the patch, SPARSEMEM page struct addresses are incorrectly calculated
    because a new section state, and an associated flag bit, has been added to
    the low bits of the mem_section.section_mem_map address; the extra bit is
    erroneously passed back as part of the section_mem_map and resultant page
    struct address, leading to errors in commands such as "kmem -p", "kmem
    -s", "kmem -n", and any other command that translates a physical address
    to its page struct address.

  * Enhancement to the S390X "vtop" command to display page table walk
    information, adding output showing the following page table contents:

       "Region-First-Table Entry" (RFTE)
       "Region-Second-Table Entry" (RSTE)
       "Region-Third-Table Entry" (RTTE)
       "Segment Table Entry" (STE)
       "Page Table Entry" (PTE)
       "Read address of page" (PAGE)

    Depending on the size of the address space, the page tables can start at
    different levels.  For example:

      crash> vtop 3ff8000c000
      VIRTUAL           PHYSICAL
      3ff8000c000       2e3832000

      PAGE DIRECTORY: 0000000000aaa000
       RTTE: 0000000000aadff8 => 00000002e3c00007
        STE: 00000002e3c00000 => 00000002e3df7000
        PTE: 00000002e3df7060 => 00000002e383203d
       PAGE: 00000002e3832000

            PAGE      PHYSICAL     MAPPING      INDEX CNT FLAGS
      3d10b8e0c80    2e3832000               0       0  1 7fffc0000000000


  * Fix the s390dbf time stamps for S390X kernel versions 4.11 and 4.14.  With
    kernel commit ea417aa8a38bc7db ("s390/debug: make debug event time stamps
    relative to the boot TOD clock") for s390dbf time is stored relative to
    the kernel boot time.  In order to still show absolute time since 1970 we
    have to detect those kernels and re-add the boot time before printing the
    records.  We can use the tod_to_timeval() symbol to check for those
    kernels because the patch has removed the symbol.  With kernel commit
    6e2ef5e4f6cc5734 ("s390/time: add support for the TOD clock epoch
    extension") the symbol name for storing the boot time has changed from
    "sched_clock_base_cc" to "tod_clock_base".  This commit is currently on
    the s390 features branch and will be integrated in Linux 4.14.

  * Further enhancement to the S390X "vtop" command to translate the binary
    values of the hardware flags for region, segment and page table entries.
    For example:

      crash> vtop -u 0x60000000000000 VIRTUAL           PHYSICAL
      60000000000000    5b50a000

      PAGE DIRECTORY: 000000005cea0000 RFTE: 000000005cea0018 =>
      000000006612400f (flags = 00f) flags in binary : P=0; TF=00; I=0; TT=11;
      TL=11 RSTE: 0000000066124000 => 000000005d91800b (flags = 00b) flags in
      binary : P=0; TF=00; I=0; TT=10; TL=11 RTTE: 000000005d918000 =>
      000000006615c007 (flags = 007) flags in binary : FC=0; P=0; TF=00; I=0;
      CR=0; TT=01; TL=11 STE: 000000006615c000 => 000000005ce48800 (flags =
      800) flags in binary : FC=0; P=0; I=0; CS=0; TT=00 PTE: 000000005ce48800
      => 000000005b50a03f (flags = 03f) flags in binary : I=0; P=0 PAGE:
      000000005b50a000

    or for large pages:

      crash> vtop -k 0x3d100000000 VIRTUAL           PHYSICAL 3d100000000
      77c00000

      PAGE DIRECTORY: 0000000001210000 RTTE: 0000000001213d10 =>
      0000000077dc4007 (flags = 007) flags in binary : FC=0; P=0; TF=00; I=0;
      CR=0; TT=01; TL=11 STE: 0000000077dc4000 => 0000000077c03403 (flags =
      03403) flags in binary : AV=0, ACC=0011; F=0; FC=1; P=0; I=0; CS=0;
      TT=00


  * PPC64 kernel commit 2f18d533757da3899f4bedab0b2c051b080079dc lowered the
    max real address to 53 bits.  Without this patch, the warning message
    "WARNING: cannot access vmalloc'd module memory" appears during
    initialization, and any command that attempts to read a vmalloc'd kernel
    virtual address will fail and display "read error" messages.

  * Display the KASLR relocation value warning message whenever it is in use.
    Without the patch, the message may not get displayed if the --kaslr option
    is used, or if the dumpfile is a vmcore generated by the current snap.so
    extension module, which now exports the relocation value in the header.

  * Fix to prevent an initialization-time failure when running a live session
    on a host system that does not have a "/usr/src" directory.  Without the
    patch, the session fails with the message "*** Error in 'crash': free():
    invalid pointer: <address> ***".  (Lei Chen)

  * Fix for the ARM64 "bt" command's display of the user mode exception frame
    at the top of the stack in Linux 4.7 and later kernels.  Without the
    patch, the contents of the user mode exception frame are invalid due to
    the miscalculation of the starting address of the pt_regs structure on the
    kernel stack.

  * Integrated support for usage of the Linux 4.14 ORC unwinder by the x86_64
    "bt" command.  Kernels configured with CONFIG_ORC_UNWINDER contain
    .orc_unwind and .orc_unwind_ip sections that can be queried to determine
    the stack frame size of any text address within a kernel function.  For
    kernels not configured with CONFIG_FRAME_POINTER, the crash utility does
    frame size calculation by disassembling a function from its beginning to
    the specified text address, counting the push, pop, and add/sub rsp
    instructions, accounting for retq instructions that occur in the middle of
    a function.  With this patch, access to the new ORC sections has been
    plugged into the existing frame size calculator, resulting in a more
    efficient and accurate manner of determining frame sizes, and as a result,
    more accurate backtraces.

  * Fix for the ARM64 "bt" command when run against Linux 4.14-rc1.  Without
    the patch, a message indicating "crash: builtin stackframe.sp offset
    incorrect!" is issued during session initialization, and the "bt" command
    fails with the error message "bt: invalid structure member offset:
    task_struct_thread_context_sp".

  * For for the "task -R <member>" option on Linux 4.13 and later kernels
    where the task_struct contains a "randomized_struct_fields_start" to
    "randomized_struct_fields_end" section.  Without the patch, a member
    argument that is inside the randomized section is not found.

  * Fix for the "snap.so" extension module to pass the value of the ARM64
    "kimage_voffset" value in the ELF header.  Without the patch, it is
    necessary to use the "--machdep kvimage_offset=<value>" command line
    option, or the session fails with the message "crash: vmlinux and vmcore
    do not match!".

 -- Troy Heber <email address hidden>  Sun, 17 Dec 2017 08:25:06 -0700

Available diffs

• diff from 7.1.9-1 to 7.2.0-1 (24.2 KiB)

crash (7.1.4-1ubuntu4.2) xenial; urgency=medium

  [ Marcelo Henrique Cerri ]
  * [Hyper-V] 16.04 kexec-tools doesn't match linux-azure (LP: #1712867)
    d/p/0011-Fix-for-Linux-commit-0100301bfdf56a2a370c7157b5ab0fb.patch
    d/p/0012-Fix-for-the-ps-t-option-in-3.17-and-later-kernels-th.patch
    d/p/0013-Fix-for-the-irq-s-option-for-Linux-4.2-and-later-ker.patch
    d/p/0014-Improvement-of-the-accuracy-of-the-allocated-objects.patch
    d/p/0015-When-reading-a-task-s-task_struct.flags-field-check-.patch
    d/p/0016-Fix-for-Linux-4.8-rc1-commit-500462a9de657f86edaa102.patch
    d/p/0017-Improvement-of-the-dev-d-option-to-display-I-O-stati.patch
    d/p/0018-Introduction-of-a-new-bt-v-option-that-checks-the-ke.patch
    d/p/0019-Fix-for-Linux-4.9-rc1-commits-15f4eae70d365bba26854c.patch
    d/p/0020-Fix-for-Linux-4.10-commit-7fd8329ba502ef76dd91db561c.patch
    d/p/0021-Prepare-for-the-kernel-s-taint_flag.true-and-taint_f.patch
    d/p/0022-Prevent-the-livepatch-taint-flag-check-during-the-sy.patch

 -- Stefan Bader <email address hidden>  Tue, 12 Sep 2017 09:15:25 +0200

Available diffs

• diff from 7.1.4-1ubuntu4.1 (in Ubuntu) to 7.1.4-1ubuntu4.2 (16.1 KiB)
• diff from 7.1.4-1ubuntu4.2~rc1 to 7.1.4-1ubuntu4.2 (139.4 KiB)

crash (7.1.9-1) unstable; urgency=medium

  * Patch from Balint Reczey <email address hidden>: Build crash on all Linux
    architectures (Closes: #763856, #757450)

  * Patch from Balint Reczey <email address hidden>: Continuous integration
    tests can fail due to missing packages for the running kernel and missing
    *-updates packages (Closes: #869367)

  * Fixes to address three gcc-7.0.1 compiler warnings that are generated when
    building with "make warn".  The warning types are "[-Wnonnull]" in
    filesys.c, and "[-Wformat-overflow=]" in kernel.c and cmdline.c.

  * Fix for the PPC64 "mach -o" option to update the OPAL console buffer size
    from 256K to 1MB, based upon the latest skiboot firmware source.

  * Fix for the "mod -[sS]" option to prevent the erroneous reassignment of
    one or more symbol values of a kernel module.  Without the patch, when
    loading a kernel module, a message may indicate "mod: <module>: last
    symbol: <symbol> is not _MODULE_END_<module>?" may be displayed, and one
    or more symbols may be reassigned an incorrect symbol value.  If none of
    the erroneous symbol value reassignments are beyond the end of the
    module's address space, then there will be no message.

  * Linux 4.10 commit 401721ecd1dcb0a428aa5d6832ee05ffbdbffbbe finally exports
    the x86_64 "phys_base" value in the VMCOREINFO note, so utilize it
    whenever it exists.

  * Implemented a new "log -a" option that dumps the audit logs remaining in
    kernel audit buffers that have not been copied out to the user-space audit
    daemon.

  * Fix for the "kmem <address>" option and the "search" command in x86_64
    kernels that contain, or have backports of, kernel commit
    7c1da8d0d046174a4188b5729d7579abf3d29427, titled "crypto: sha - SHA1
    transform x86_64 AVX2", which introduced an "_end" text symbol.  Without
    the patch, if a base kernel symbol address that is larger than the "_end"
    text symbol is passed to "kmem <address>", its symbol/filename information
    will not be displayed.  Also, when the "search" command scans the
    __START_KERNEL_map region that contains kernel text and static data, the
    search will be truncated to stop at the "_end" text symbol address.

  * Enhancement for the determination of the ARM64 "kimage_voffset" value in
    Linux 4.6 and later kernels if an ELF format dumpfile does not contain its
    value in a VMCOREINFO note, or when running against live systems using
    /dev/mem, /proc/kcore, or an older version of /dev/crash.

  * Optimization of the "kmem -f <address>" and "kmem <r;address>" options to
    significantly reduce the amount of time to complete the buddy allocator
    free-list scan for the target address.  On very large memory systems, the
    patch may reduce the time spent by several orders of magnitude.

  * Fix for a compilation error if glibc-2.25 or later has been installed on
    the host build machine.  Without the patch, the build fails with the error
    message "amd64-linux-nat.c:496:1: error: conflicting types for
    'ps_get_thread_area'".

  * Fix for the "list -[hH]" options if a list_head.next pointer is
    encountered that contains an invalid NULL pointer.  Without the patch, the
    "list -[hH]" options would complete/continue as if the NULL were a
    legitimate end-of-list indicator, and no error would be reported.

  * Provide basic Huge Page usage as part of "kmem -i" output, showing the
    total amount of memory allocated for huge pages, and the amount of the
    total that is free.

  * Fix for the determination of the x86_64 "phys_base" value when it is not
    passed in the VMCOREINFO data of ELF vmcores.  Without the patch, it is
    possible that the base address of the vmalloc region is unknown and
    initialized to an incorrect default address during the very early stages
    of initialization, which causes the parsing of the PT_LOAD segments for
    the START_KERNEL_map region to fail.

  * Fix for the "dis" command to detect duplicate symbols in the case of a
    "symbol+offset" argument where the duplicates are contiguous in the symbol
    list.  In addition, reject "symbol+offset" arguments if the resultant
    address goes beyond the end of the function.

  * Fix for the "set scope" option if the kernel was configured with
    CONFIG_RANDOMIZE_BASE.  Without the patch, the command fails with the
    message "set: gdb cannot find text block for address: <symbol>".  This
    also affects extension modules that call gdb_set_crash_scope() when
    running with KASLR kernels.

  * Fix for the extensions/trace.c extension module to account for Linux 4.7
    kernel commit 9b94a8fba501f38368aef6ac1b30e7335252a220, which changed the
    ring_buffer_per_cpu.nr_pages member from an int to a long.  Without the
    patch, the trace.so extension module fails to load on big-endian machines,
    indicating "extend: Num of pages is less than 0".

  * Fix for the extensions/trace.c extension module when running on the ppc64
    architecture.  Without the patch, the trace.so extension module fails to
    load, indicating "extend: invalid text address: ring_buffer_read".  On the
    ppc64 architecture, the text symbol is ".ring_buffer_read".

  * Fix for the ARM64 "bt" command.  Without the patch, the backtrace of a
    non-panicking active task generates a segmentation violation when
    analyzing Android 4.4-based dumpfiles.

 -- Troy Heber <email address hidden>  Wed, 26 Jul 2017 12:37:08 -0600

Available diffs

• diff from 7.1.8-1ubuntu2 (in Ubuntu) to 7.1.9-1 (17.1 KiB)

crash (7.1.8-1ubuntu2) artful; urgency=medium

  * Use only available repository pockets in autopkgtest (LP: #1693387)
  * Use isolation-machine in autopkgtest to ensure that the running
    kernel has available debug packages in the archive in use

 -- Balint Reczey <email address hidden>  Tue, 13 Jun 2017 12:50:26 +0200

Available diffs

• diff from 7.1.8-1ubuntu1 to 7.1.8-1ubuntu2 (918 bytes)

crash (7.1.8-1ubuntu1) zesty; urgency=medium

  * Merge from Debian unstable (LP: #1672361).  Remaining changes:
    - Build for armhf, ppc64el.
    - Minor fixes for live autopkgtest.

 -- Stefan Bader <email address hidden>  Fri, 17 Mar 2017 14:03:05 +0100

Available diffs

• diff from 7.1.7-1ubuntu2 to 7.1.8-1ubuntu1 (27.8 KiB)

crash (7.1.4-1ubuntu4.1) xenial; urgency=medium

  * Cherry-pick upstream commit to complete support for 4.5+ kernels :
    d/p/0003-Fix-for-the-replacements-made-to-the-kernel-s-cpu_po.patch,
    d/p/0004-With-the-introduction-of-radix-MMU-in-Power-ISA-3.0-.patch,
    d/p/0005-Fix-for-Linux-commit-0139aa7b7fa12ceef095d99dc36606a.patch,
    d/p/0006-Fix-for-Linux-commit-edf14cdbf9a0e5ab52698ca66d07a76.patch,
    d/p/0007-Fix-to-recognize-and-support-x86_64-Linux-4.8-rc1-an.patch,
    d/p/0008-Fix-for-a-possible-segmentation-violation-when-analy.patch,
    d/p/0009-Fix-for-support-of-Linux-4.7-and-later-x86_64-ELF-kd.patch,
    d/p/0010-Linux-3.15-and-later-kernels-configured-with-CONFIG_.patch
    These commits are included in version 7.1.7 of crash and are required
    in order to correctly open 4.5 kernels and newer (LP: #1655625).

 -- Louis Bouchard <email address hidden>  Fri, 20 Jan 2017 17:53:30 +0100

Available diffs

• diff from 7.1.4-1ubuntu4 to 7.1.4-1ubuntu4.1 (12.3 KiB)

crash (7.1.7-1ubuntu2) zesty; urgency=medium

  * d/p/0001-Fix-for-Linux-4.6-commit-b03a017bebc403d40aa53a092e7.patch :
    Fix additional kernel 4.6 issue introduced post-7.1.7 release.
  * d/p/0002-Fix-for-support-of-proc-kcore-as-the-live-memory-sou.patch :
    Fix live crash usage failure identified by autopkgtest. This commit was
    introduced post-7.1.7 release.

 -- Louis Bouchard <email address hidden>  Thu, 19 Jan 2017 16:01:27 +0100

Available diffs

• diff from 7.1.5-1ubuntu1 to 7.1.7-1ubuntu2 (66.3 KiB)
• diff from 7.1.7-1ubuntu1 to 7.1.7-1ubuntu2 (3.1 KiB)

crash (7.1.7-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable. (LP: #1657488)  Remaining changes:
    - Build for armhf, ppc64el.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.
    - Simplify ddeb archive requirements.

Available diffs

• diff from 7.1.5-1ubuntu2 to 7.1.7-1ubuntu1 (70.7 KiB)

crash (7.0.3-3ubuntu4.5) trusty; urgency=medium

  * Fix for: Unable to analyse vmcore/dump via crash due to bad kernel
    debug info build (LP: #1607894).

 -- Robert Hooker <email address hidden>  Thu, 01 Dec 2016 12:03:17 -0500

Available diffs

• diff from 7.0.3-3ubuntu4.4 to 7.0.3-3ubuntu4.5 (1.5 KiB)

crash (7.1.5-1ubuntu2) yakkety; urgency=medium

  * Crash cannot parse Linux 4.8 vmcore files on ppc64el. (LP: #1628173)

 -- Chris J Arges <email address hidden>  Tue, 27 Sep 2016 14:58:43 -0500

Available diffs

• diff from 7.1.5-1ubuntu1 to 7.1.5-1ubuntu2 (7.5 KiB)

crash (7.1.5-1ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Build for armhf, arm64, ppc64el.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.
    - Simplify ddeb archive requirements.
  * Dropped patches:
    - 0001-Fix-for-the-changes-made-to-the-kernel-module-struct.patch
    - 0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch

 -- Chris J Arges <email address hidden>  Tue, 03 May 2016 06:23:16 -0500

Available diffs

• diff from 7.1.4-1ubuntu4 to 7.1.5-1ubuntu1 (44.4 KiB)

crash (7.1.4-1ubuntu4) xenial; urgency=medium

  * d/p/0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch:
    Cherry-pick additional crash commit needed to fix issues related to
    kernel commit 8244062e. (LP: #1564487)

 -- Chris J Arges <email address hidden>  Fri, 01 Apr 2016 08:46:07 -0500

Available diffs

• diff from 7.1.4-1ubuntu3 to 7.1.4-1ubuntu4 (1.1 KiB)

crash (7.1.4-1ubuntu3) xenial; urgency=medium

  * debian/tests/live: Use the new ddebs.ubuntu.com key C8CAB6595FDFF622

 -- Adam Conrad <email address hidden>  Mon, 21 Mar 2016 09:01:57 -0600

Available diffs

• diff from 7.1.4-1ubuntu2 to 7.1.4-1ubuntu3 (546 bytes)

crash (7.1.4-1ubuntu2) xenial; urgency=medium

  * d/p/0001-Fix-for-the-changes-made-to-the-kernel-module-struct.patch:
    Fix launch failure on kernel newer than 4.4 (LP: #1555244)

 -- Louis Bouchard <email address hidden>  Thu, 10 Mar 2016 15:38:01 +0100

Available diffs

• diff from 7.1.4-1ubuntu1 to 7.1.4-1ubuntu2 (1.2 KiB)

crash (7.1.4-1ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Build for armhf, arm64, ppc64el.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.
    - Simplify ddeb archive requirements.
  * Dropped patches:
    - 4_2_support.patch

Available diffs

• diff from 7.1.1-1ubuntu5 to 7.1.4-1ubuntu1 (64.4 KiB)

crash (7.0.3-3ubuntu4.4) trusty; urgency=medium

  * Fix for crash: page excluded: kernel virtual address: ffff881052fa8000
    type: "fill_task_struct" (LP: #1523606)

 -- Dave Chiluk <email address hidden>  Mon, 07 Dec 2015 11:38:05 -0600

Available diffs

• diff from 7.0.3-3ubuntu4.3 to 7.0.3-3ubuntu4.4 (1.0 KiB)

crash (7.0.8-1ubuntu3.2) vivid; urgency=medium

  * Fix for crash: page excluded: kernel virtual address: ffff881052fa8000
    type: "fill_task_struct" (LP: #1523606)

 -- Dave Chiluk <email address hidden>  Tue, 15 Dec 2015 16:18:33 -0600

Available diffs

• diff from 7.0.8-1ubuntu3.1 to 7.0.8-1ubuntu3.2 (1.0 KiB)

crash (7.1.1-1ubuntu4.1) wily; urgency=medium

  * Fix for crash: page excluded: kernel virtual address: ffff881052fa8000
    type: "fill_task_struct" (LP: #1523606)

 -- Dave Chiluk <email address hidden>  Tue, 15 Dec 2015 16:31:54 -0600

Available diffs

• diff from 7.1.1-1ubuntu4 to 7.1.1-1ubuntu4.1 (1018 bytes)

crash (7.1.1-1ubuntu5) xenial; urgency=medium

  * Fix for crash: page excluded: kernel virtual address: ffff881052fa8000
    type: "fill_task_struct" (LP: #1523606)

 -- Dave Chiluk <email address hidden>  Tue, 15 Dec 2015 16:31:54 -0600

Available diffs

• diff from 7.1.1-1ubuntu4 to 7.1.1-1ubuntu5 (1020 bytes)

crash (7.1.1-1ubuntu4) wily; urgency=medium

  * debian/tests/live: Enable -proposed apt sources.

 -- Martin Pitt <email address hidden>  Tue, 15 Sep 2015 10:12:50 +0200

Available diffs

• diff from 7.1.1-1ubuntu3 to 7.1.1-1ubuntu4 (470 bytes)

crash (7.0.3-3ubuntu4.3) trusty; urgency=medium

  * Fix-for-the-PPC64-bt-command-on-both-big-endian-and-.patch (LP: #1429250)
  * Remove extraneous patch:
      0001-Implemented-support-for-the-ARM64-bt-l-option.patch

 -- Chris J Arges <email address hidden>  Mon, 10 Aug 2015 16:44:48 -0500

Available diffs

• diff from 7.0.3-3ubuntu4.2 to 7.0.3-3ubuntu4.3 (2.5 KiB)

crash (7.0.8-1ubuntu3.1) vivid; urgency=medium

  * Fix-for-the-ARM64-page-size-determination-on-Linux-4.patch. (LP: #1460941)

 -- dann frazier <email address hidden>  Tue, 23 Jun 2015 09:09:54 -0500

Available diffs

• diff from 7.0.8-1ubuntu3 to 7.0.8-1ubuntu3.1 (1.3 KiB)

crash (7.0.8-1ubuntu1.2) utopic; urgency=medium

  * Fix-for-the-ARM64-page-size-determination-on-Linux-4.patch. (LP: #1460941)

 -- dann frazier <email address hidden>  Tue, 23 Jun 2015 09:30:46 -0500

Available diffs

• diff from 7.0.8-1ubuntu1.1 to 7.0.8-1ubuntu1.2 (1.3 KiB)

crash (7.0.3-3ubuntu4.2) trusty; urgency=medium

  * Initial-working-implementation-of-the-basic-ARM64-bt.patch,
    Cleaned-up-the-exception-frame-displays-of-64-bit-in.patch,
    Implemented-support-for-the-ARM64-bt-e-option.patch,
    Implemented-support-for-the-ARM64-bt-l-option.patch:
     - Add initial ARM64 support for the 'bt' command. (LP: #1466686)
  * Fix-for-the-ARM64-page-size-determination-on-Linux-4.patch. (LP: #1460941)

 -- dann frazier <email address hidden>  Tue, 23 Jun 2015 09:37:27 -0500

Available diffs

• diff from 7.0.3-3ubuntu4.1 to 7.0.3-3ubuntu4.2 (5.2 KiB)

crash (7.1.1-1ubuntu3) wily; urgency=medium

  * debian/tests/live: Make apt-get install non-interactive.

 -- Chris J Arges <email address hidden>  Wed, 03 Jun 2015 17:05:48 -0500

Available diffs

• diff from 7.1.1-1ubuntu2 to 7.1.1-1ubuntu3 (516 bytes)

crash (7.1.1-1ubuntu2) wily; urgency=medium

  * debian/tests/live: Redirect crash stderr to stdout. The CONFIG_STRICT_DEVMEM
    warning is known and expected.

 -- Chris J Arges <email address hidden>  Wed, 03 Jun 2015 13:26:47 -0500

Available diffs

• diff from 7.1.1-1ubuntu1 to 7.1.1-1ubuntu2 (426 bytes)

crash (7.1.1-1ubuntu1) wily; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Build for armhf, arm64, ppc64el.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.
    - Simplify ddeb archive requirements.
  * Dropped patches:
    - Fix-for-the-PPC64-bt-command-on-both-big-endian-and-.patch
    - Linux-4.0.patch

 -- Chris J Arges <email address hidden>  Tue, 02 Jun 2015 09:12:52 -0500

Available diffs

• diff from 7.0.8-1ubuntu3 to 7.1.1-1ubuntu1 (120.2 KiB)

crash (7.0.3-3ubuntu4.1) trusty; urgency=medium

  * Linux-4.0.patch: Backport support for 4.0+ kernel versions. (LP: #1444528)
 -- Chris J Arges <email address hidden>   Wed, 22 Apr 2015 13:36:49 -0500

Available diffs

• diff from 7.0.3-3ubuntu4 to 7.0.3-3ubuntu4.1 (1008 bytes)

crash (7.0.8-1ubuntu1.1) utopic; urgency=medium

  * Linux-4.0.patch: Support 4.0+ kernel versions. (LP: #1444528)
 -- Chris J Arges <email address hidden>   Wed, 22 Apr 2015 13:51:24 -0500

Available diffs

• diff from 7.0.8-1ubuntu1 to 7.0.8-1ubuntu1.1 (860 bytes)

crash (7.0.8-1ubuntu3) vivid; urgency=medium

  * Linux-4.0.patch: Support 4.0+ kernel versions. (LP: #1444528)
 -- Chris J Arges <email address hidden>   Wed, 15 Apr 2015 10:12:21 -0500

Available diffs

• diff from 7.0.8-1ubuntu2 to 7.0.8-1ubuntu3 (898 bytes)

crash (7.0.8-1ubuntu2) vivid; urgency=medium

  * Fix-for-the-PPC64-bt-command-on-both-big-endian-and-.patch (LP: #1429250)
 -- Chris J Arges <email address hidden>   Tue, 07 Apr 2015 13:52:16 -0500

Available diffs

• diff from 7.0.8-1ubuntu1 to 7.0.8-1ubuntu2 (1.7 KiB)

crash (7.0.8-1ubuntu1) utopic; urgency=medium

  * FFe LP: #1381999.
    - 7.0.8 adds upstream support for new architectures
    - fixing ftbfs on arm64.
  * Merge with Debian; remaining changes:
    - Build for armhf, arm64, ppc64el.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.

Available diffs

• diff from 7.0.7-1ubuntu1 to 7.0.8-1ubuntu1 (114.9 KiB)

crash (7.0.3-3ubuntu4) trusty-proposed; urgency=medium

  * debian/patches/Updated-the-ARM64-implementation-to-support-Linux-3..patch:
    Basic support >= 3.13 kernels on arm64. (LP: #1354349).
 -- dann frazier <email address hidden>   Tue, 30 Sep 2014 15:04:06 -0600

Available diffs

• diff from 7.0.3-3ubuntu3 to 7.0.3-3ubuntu4 (3.2 KiB)

crash (7.0.7-1ubuntu1) utopic; urgency=medium

  * Merge with Debian; remainging changes:
    - Build for armhf, arm64.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.
    - Add ppc64el support.

Available diffs

• diff from 7.0.5-1ubuntu1 to 7.0.7-1ubuntu1 (48.6 KiB)

crash (7.0.3-3ubuntu3) trusty-proposed; urgency=medium

  * Build crash for ppc64el. LP: #1318809.
  * Add ppc64el support (debian/control, debian/rules (for patches),
    gdb-7.6-ppc64el.patch); patch-set provided by Bharata Rao.
 -- Mauricio Faria de Oliveira <email address hidden>   Fri, 16 May 2014 08:52:26 -0300

Available diffs

• diff from 7.0.3-3ubuntu2 to 7.0.3-3ubuntu3 (38.5 KiB)

crash (7.0.5-1ubuntu1) utopic; urgency=medium

  * Merge with Debian; remaining changes:
    - Build for armhf, arm64.
    - Minor fixes for live autopkgtest.
    - debian/tests/live: Redirect gpg stderr to stdout, as that's the only
      known and expected stderr source.
  * Add ppc64el support (Bharata Rao, Mauricio Faria de Oliveira).

Available diffs

• diff from 7.0.3-3ubuntu2 to 7.0.5-1ubuntu1 (90.8 KiB)

crash (7.0.3-3ubuntu2) trusty; urgency=low

  * debian/tests/live: Previous merge dropped the "allow-stderr" restriction.
    Redirect gpg stderr to stdout, as that's the only known and expected
    stderr source.
 -- Martin Pitt <email address hidden>   Thu, 21 Nov 2013 09:47:25 +0100

Available diffs

• diff from 6.1.6-1ubuntu2 to 7.0.3-3ubuntu2 (11.2 MiB)
• diff from 7.0.3-3ubuntu1 to 7.0.3-3ubuntu2 (586 bytes)

crash (7.0.3-3ubuntu1) trusty; urgency=low

  * Merge with Debian; remaining changes:
    - Build for armhf, arm64.
  * Minor fixes for live autopkgtest.

Available diffs

• diff from 7.0.2-1ubuntu1 to 7.0.3-3ubuntu1 (23.2 KiB)

crash (7.0.2-1ubuntu1) trusty; urgency=low

  * Merge with Debian; remaining changes:
    - Build for armhf.
    - Add a live autopkgtest to run crash on running kernel.
  * Build for AArch64.

Available diffs

• diff from 6.1.6-1ubuntu2 to 7.0.2-1ubuntu1 (11.2 MiB)

crash (6.1.6-1ubuntu2) saucy; urgency=low

  * Add a live autopkgtest to run crash on running kernel.
 -- Chris J Arges <email address hidden>   Tue, 27 Aug 2013 12:37:03 -0500

Available diffs

• diff from 6.1.6-1ubuntu1 to 6.1.6-1ubuntu2 (933 bytes)

crash (6.1.6-1ubuntu0.13.04.1) raring-proposed; urgency=low

  * Merge from Debian unstable (LP: #1064475). Remaining changes:
    - debian/rules: Always build extensions and package them.
    - debian/rules: Cleanup for extensions.
  * Dropped ubuntu changes:
    - SPU extension support.
  * debian/control: Add armhf to build architectures.

Available diffs

• diff from 6.1.0-1ubuntu2 to 6.1.6-1ubuntu0.13.04.1 (76.1 KiB)

crash (6.1.6-1ubuntu0.12.10.1) quantal-proposed; urgency=low

  * Merge from Debian unstable (LP: #1064475). Remaining changes:
    - debian/rules: Always build extensions and package them.
    - debian/rules: Cleanup for extensions.
  * Dropped ubuntu changes:
    - SPU extension support.
  * debian/control: Add armhf to build architectures.

Available diffs

• diff from 5.1.6-1ubuntu1 to 6.1.6-1ubuntu0.12.10.1 (7.9 MiB)