[ANNOUNCE] crash version 4.1.1 is available

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 - Fix for a potential session initialization failure when running 
   against 2.6.30 or later x86_64 kernel dumpfiles whose pages have been
   filtered by the the makedumpfile facility.  Without the patch, the
   session may fail with the error message "crash: page excluded: kernel
   virtual address: <address>  type: cpu number (per_cpu)", but will
   initialize OK if the "--zero_excluded" command line option is used.
   (anderson@xxxxxxxxxx)

 - Added "lsmod" as a built-in alias for the "mod" command.
   (anderson@xxxxxxxxxx)

 - Added a defensive mechanism to handle corrupt Elf32_Nhdr/Elf64_Nhdr
   structures in an ELF vmcore.  The fix no longer presumes that all
   Elf32_Nhdr/Elf64_Nhdr structure contents are legitimate, and if an
   invalid Elf32_Nhdr or Elf64_Nhdr structure is encountered, it will 
   be ignored and a warning message will be displayed showing the 
   structure contents, and the crash session will continue on.  Without
   the patch, it was possible that an invalid  n_namesz or n_descsz 
   value could cause a segmentation violation when attempting to read 
   the bogus note contents.
   (anderson@xxxxxxxxxx)

 - Fix for "mach -c" command option on 2.6.30 and later x86_64 kernels
   in which the per-cpu array x8664_pda data structures were replaced 
   with per-cpu variables.  Without the patch, the command displays 
   just the boot cpu's cpuinfo data structure and then fails with the
   error message: "mach: invalid structure name: x8664_pda".
   (anderson@xxxxxxxxxx) 

 - Fix to properly set the DEBUG exception stack size and stack base
   address on 2.6.18 and later x86_64 kernels.  Without the patch, the
   DEBUG exception stack was presumed to be the same size as all of the
   other exception stacks, so in the extremely rare occurrance that a 
   kernel crash started while running on a per-cpu DEBUG stack, the 
   backtrace code would not recognize it as such, and would either start
   the trace using stale starting stack hooks, typically from "schedule"
   while running on the process stack, or the backtrace attempt would 
   fail with the error message "bt: cannot transition from exception 
   stack to current process stack".
   (anderson@xxxxxxxxxx)

 - Related to the above, when the x86_64 "bt" is displaying a trace
   segment from one of the five exception stacks, change the output from 
   showing just "--- <exception stack> ..." to showing which exception 
   stack it's working from, for example, "--- <NMI exception stack> ---"
   or "--- <DEBUG exception stack> ---", etc.
   (anderson@xxxxxxxxxx)

 - Fix for a session initialization failure when running against 2.6.30
   or later x86_64 kernels if the number of possible cpus equals the
   kernel's configured NR_CPUS.  Without the patch, the session fails 
   with the error message "crash: invalid kernel virtual address: cc08
   type: cpu number (per_cpu)".
   (bob.montgomery@xxxxxx)

 - Preparations in the top-level source code for the integration of 
   gbd-7.0.  The current embedded version remains gdb-6.1.
   (anderson@xxxxxxxxxx)

 Download from: http://people.redhat.com/anderson

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility

[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux