SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

 
 
Changelog for crash-debugsource-7.1.5-1.2.x86_64.rpm :

* Mon Aug 15 2016 ptesarikAATTsuse.com- crash-linux-4.6-printk-flags.patch: Fix warning \"failed to read pageflag_names entry\" on Linux 4.6 (bsc#978601).
* Fri May 27 2016 ptesarikAATTsuse.com- eppic-support-arm64.patch: Support for ARM64 (FATE#320844).
* Tue May 24 2016 dmairAATTsuse.de- Upgrade of source tarball to 7.1.5 from upstream and fix of refresh of patches to align with the version. For a detailed changelog of the source tarball see: http://people.redhat.com/anderson/crash.changelog.html includes a fix for bsc#977306. Feature enhancements include: - \"whatis -r\" and \"whatis -m\" commands that allow search for data structure of a specified size and that contains a member of a given type respectively.
* Fri Jan 22 2016 lpechacekAATTsuse.com- Disable RT KMP build (bsc#962719)
* Wed Oct 07 2015 lpechacekAATTsuse.com- Enable RT KMP build (bsc#948840)
* Thu Oct 01 2015 dmairAATTsuse.com- For 7.1.3 ppc64le the following patches are obsoleted by mainline crash-gdb-7.6-add-powerpc64le-linux.patch crash-gdb-7.6-bound_minimal_symbol.patch crash-gdb-7.6-floatformat.patch crash-gdb-7.6-ppc64-ELFv2-trampoline-match.patch crash-gdb-7.6-ppc64_sysv_abi_push_float.patch crash-gdb-7.6-ppc64le.patch crash-gdb-7.6-ppc_insns_match_pattern.patch crash-gdb-7.6-update-autoconf-2013-04-24.patch crash-gdb-7.6-update-autoconf-2013-06-10.patch crash-gdb-7.6.series crash-patch-gdb.patch
* Tue Sep 22 2015 dmairAATTsuse.com- Update to 7.1.3 (bsc#946458) o Introduction of \"dis -f
\" which disassembles from the address to the end of the function o Introduction of \"dis -s
\" which displays the filename and line number associated with the specified text location, followed by a source code listing if available. o Addition of a new \"--src \" command line option for use by the \"dis -s\" option if the kernel source is not located in the standard location. o Do not search for a panic task in s390x dumpfiles that are marked as a \"live dump\" o Fix unnecessary error messages when a directory is used as a command line argument o See http://people.redhat.com/anderson/crash.changelog.html for the complete changelog- Removed these patches obsoleted by mainline: crash-x86_64-nested-nmi.patch crash-keep-file-orig-with-name-on-select.patch crash-kmem_cache-downsize.patch crash-s390x-add-vector-support.patch- Refreshed patches
* Wed Jul 29 2015 ptesarikAATTsuse.cz- crash-move-xen-dom0-handling-into-own-file.patch: Move Xen Dom0 handling into xen_dom0.c (FATE#316467).- crash-move-xen-p2m-map.patch: Move xen p2m map initialization to xen_kdump_p2m (FATE#316467).- crash-use-xen_machine_addr-command.patch: Use XEN_MACHINE_ADDR command flag instead of overriding readmem (FATE#316467).- crash-move-xen-elf-note-processing.patch: Move Xen ELF note processing to xen_dom0.c (FATE#316467).- crash-add-xen-dom0-support-for-kdump.patch: Add Xen Dom0 support for kdump compressed files (FATE#316467).
* Tue Jul 21 2015 ptesarikAATTsuse.com- crash-s390x-add-vector-support.patch: SIMD support for dump tools (z13) (FATE#318058).
* Thu Sep 04 2014 ptesarikAATTsuse.cz- crash-kmem_cache-downsize.patch: Fix kmem slab initialization failures (bnc#885082).
* Mon Aug 18 2014 ptesarikAATTsuse.cz- Module.supported: mark crash.ko supported (bnc#891375).
* Thu Jul 31 2014 dimstarAATTopensuse.org- Rename rpmlintrc to %{name}-rpmlintrc. Follow the packaging guidelines.
* Thu Jun 12 2014 dmairAATTsuse.de- crash-keep-file-orig-with-name-on-select.patch Fix the namelist selection for gdb to have background state used to select file to delete for expansion of compressed file (bnc#877367)
* Fri May 16 2014 ptesarikAATTsuse.cz- crash_enable_snappy_support.patch: enable snappy support.
* Wed Apr 30 2014 ptesarikAATTsuse.cz- crash-x86_64-nested-nmi.patch: Fix NMI backtrace for kernels patched to handle nested NMIs (bnc#874179).
* Sat Apr 12 2014 mmarekAATTsuse.cz- Add # needssslcertforbuild to use the project\'s certificate when building in a home project.
* Tue Feb 18 2014 dmairAATTsuse.de- Implementation of 7.0.5 from upstream, including patch refresh Changelog: - Fix for the \"runq -g\" option for kernels that are configured with CONFIG_FAIR_GROUP_SCHED, but not CONFIG_CFS_BANDWIDTH. Without the patch, the command fails with the message \"runq: invalid structure member offset: cfs_rq_throttled\". (vinayakm.listAATTgmail.com) - Add support for Xen PVH guest types introduced in Xen 4.4. Without the patch, running against a Xen 4.4 hypervisor binary would fail during session initialization with the error message \"crash: invalid structure member offset: domain_is_hvm\". In addition, the PVH guest type is being registered internally as an HVM guest type, the debug \"help -X ofs\" command\'s display of the domain_domain_flags offset has been fixed to show it in decimal, and the setting of the internal dc->domain_flags has been fixed to contain all flags set, not just the first one found. (dslutzAATTverizon.com) - Fix for the \"kmem -S\" command on Linux 3.1 and later kernels that are configured with CONFIG_SLUB. Because the the page structure\'s inuse and objects fields used by SLUB were changed from discrete u16 types to bit-fields within an unsigned int, the display of per-node partial slab statistics are incorrect. Without the patch, the TOTAL and ALLOCATED values are incorrectly shown as equal values, and therefore the FREE value is always zero. (andersonAATTredhat.com) - Fix for the \"kmem -S\" command for kernels that are configured with CONFIG_SLUB. Eash per-cpu slab object dump may show incorrect ALLOCATED and FREE values; and as seen on Linux 3.5 and later kernels, the TOTAL value and the number of individual objects dumped may also be incorrect (too small). (andersonAATTredhat.com) - When executing the commands from an input file specified by the \"-i \" command line option, or when accepting input from a file as a set of commands or as a set of command arguments using the \"<\" redirection character, unconditionally cease the operation if CTRL-c is entered. Without the patch, depending upon the command that was running when the SIGINT was received, the operation may continue uninterruptibly until the file contents are consumed. (andersonAATTredhat.com) - Enhanced the \"bt -F\" option such that if \"-F\" is entered twice, and if the stack frame contents reference a slab cache object, both the slab cache name and the stack contents will be displayed within brackets. (andersonAATTredhat.com) - Enhanced the \"rd -S\" option such that if \"-S\" is entered twice, and if the memory contents reference a slab cache object, both the slab cache name and the memory contents will be displayed within brackets. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command to prevent an unwarranted message indicating \"WARNING: possibly bogus exception frame\" generated from a blocked kernel thread that was in the process of exec\'ing a user process via the call_usermodehelper() facility. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command to more correctly determine the function frame that called into an interrupted function. Without the patch, the first frame just above an IRQ exception frame register dump may show an invalid/stale function. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command if a page fault exception was generated by the invalid contents of the RIP register. Without the patch, the exception frame register dump is not displayed above the \"page_fault\" stack frame; and in a related issue, the \"bt -e\" option will not find and display the exception frame. (andersonAATTredhat.com) - When invoking a crash session with a compressed vmlinux file, make the same host-machine/vmlinux endian verification that is done with uncompressed vmlinx files. (andersonAATTredhat.com) - Reduce the number of CTRL-c entries required to unconditionally terminate any manually-entered command from three to one. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command if an async page fault exception occurred in a KVM guest running a Linux 2.6.38 or later kernel. Without the patch, the exception frame register dump is not displayed above the \"async_page_fault\" stack frame. (andersonAATTredhat.com)
* Wed Jan 29 2014 roAATTsuse.de- disable build_kmp on i586 and s390, SLE-12 does not build a runnable kernel there
* Fri Jan 24 2014 ptesarikAATTsuse.cz- Enable ppc64le: o crash-patch-gdb.patch: allow applying custom gdb patches o crash-gdb-7.6.series: series file for gdb patches o gdb-7.6-ppc64_sysv_abi_push_float.patch: backported dependency o gdb-7.6-bound_minimal_symbol.patch: dtto o gdb-7.6-add-powerpc64le-linux.patch: dtto o gdb-7.6-update-autoconf-2013-04-24.patch: dtto o gdb-7.6-ppc_insns_match_pattern.patch: dtto o gdb-7.6-floatformat.patch: dtto o gdb-7.6-ppc64-ELFv2-trampoline-match.patch: dtto o gdb-7.6-update-autoconf-2013-06-10.patch: dtto o gdb-7.6-ppc64le.patch: patch used for the gdb package
* Fri Jan 24 2014 dmairAATTsuse.com- Implementation of 7.0.4 from upstream and patch refresh.- Fix for the \"ps\" command\'s display of per-task RSS and %MEM values in Linux 2.6.34 and later kernels in which SPLIT_RSS_COUNTING is enabled. Without the patch, the values are only taken from each task\'s mm_struct.rss_stat structure, which may contain stale values because they may not be synchronized with the RSS values stored in each per-thread task_struct.rss_stat structure; this may lead to invalid or slightly low RSS values, and worst-case, the %MEM value may show garbage percentage values. (vinayakm.listAATTgmail.com)- Addressed a few (harmless) Coverity Scan complaints in diskdump.c: 1579:dead_error_line – Execution cannot reach this expression \"\"|\"\" inside statement \"fprintf(fp, \"%sDUMP_DH_COMP...\". 1574:dead_error_line – Execution cannot reach this expression \"\"|\"\" inside statement \"fprintf(fp, \"%sDUMP_HEADER_...\". 1571:dead_error_line – Execution cannot reach this expression \"\"|\"\" inside statement \"fprintf(fp, \"%sDUMP_HEADER_...\". (andersonAATTredhat.com)- Addressed two warnings when compiling diskdump.c on 32-bit architectures when the snappy library is built in: diskdump.c:1046: warning: passing argument 3 of \'snappy_uncompressed_length\' from incompatible pointer type /usr/include/snappy-c.h:120: note: expected ‘size_t
*’ but argument is of type ‘ulong
*’ diskdump.c:1056: warning: passing argument 4 of ‘snappy_uncompress’ from incompatible pointer type /usr/include/snappy-c.h:103: note: expected ‘size_t
*’ but argument is of type ‘ulong
*’ (andersonAATTredhat.com)- Created a simpler interface with the internal do_list() function. Currently, if a caller wants to gather the contents of a list into an array, it must do the following: (1) call hq_open() so that the list contents will be verified and saved in the hash queue (2) call do_list() to store the list in the hash queue and return the number of entries in the list (3) allocate a buffer to store the array of entries in the list (4) pass the allocated buffer to retrieve_list() to be populated from the hash queue (5) call hq_close() With this patch, if the passed-in list_data.flags field has a new LIST_ALLOCATE bit set, then do_list() will perform steps (1), (3), (4) and (5) above. The caller can access the allocated array via a new list_data.list_ptr member, and, when done parsing the list, the allocated buffer should be returned via FREEBUF(). The only restriction is that the hash queue cannot be currently in use, or the do_list() call will fail. It should also be noted that there are circumstances where it still makes sense that steps (1), (3), (4) and (5) are performed by the do_list() caller. (andersonAATTredhat.com)- Modified the internal parent_list() function, used by \"ps -p\", to utilize the simpler new do_list() functionality described above. (andersonAATTredhat.com)- Modified the internal dump_vmap_area() function, used by the \"kmem -v\", \"kmem
\" and \"search\" commands, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com)- Modified the internal nr_blockdev_pages() function, used by the \"kmem -i\", to utilize the simpler new do_list() functionality. (andersonAATTredhat.com)- Modified the internal get_mount_list() function, used by the \"mount\" and \"files -d\" commands, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com)- Modified the internal get_kmem_cache_list() function, used by the \"kmem -[sS]\", \"kmem
\", \"rd -S\" and \"bf -F\" commands, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com)- Modified the internal show_net_devices_v2() and show_net_devices_v3() functions, used by the \"net\" command, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com)- The \"help -r\" option has been extended to dump the X86 and X86_64 registers stored in the NT_PRSTATUS notes in netdump ELF, kdump ELF, and compressed kdump dumpfiles. Without the patch, the option only supports ELF dumpfiles created by the \"virsh dump --memory-only\" facility. (andersonAATTredhat.com)- Modified the \"runq -g\" display to show the CFS task_group and cfs_rq addresses; also the current task is also displayed in its CFS or RT queue with with the notation \"[CURRENT]\" appended to the task data. (Anthony.ChenAATTTeradata.com)- Additional modification to the \"runq -g\" to display the task_group and rt_rq addresses for the RT queues, similar in nature to the CFS queue changes are done by the patch above. In addition, the CFS rb_root and RT prio_array addresses are no longer shown given that they can be determined by looking at the cfs_rq and rt_rq structures whose addresses are now displayed. (andersonAATTredhat.com)- Modified the behavior of the \"mod -t\" option when running against Linux 2.6.18 and earlier kernels such that the hexadecimal value of the module->license_gplok member is always displayed. Without the patch, if a module\'s license_gplok boolean or bitmask value is 0, it would only be displayed if the module was unsigned. (andersonAATTredhat.com, atomlinAATTredhat.com)- Modified the internal dump_tasks_in_task_group_rt_rq() and dump_RT_prio_array() functions, used by the \"runq\" command, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com)- Resurrection of the remote analysis capability for use with the \"xen-crashd\" daemon running on a Xen Dom0 host, which communicates with a paused or shutdown DomU guest kernel. The daemon can be accessed like so: $ crash localhost:5001,/dev/xenmem vmlinux (dslutzAATTverizon.com)- Prevent the X86_64 \"bt\" command from using starting RSP and RIP values taken from the NT_PRSTATUS notes of kdump dumpfiles if the RSP address is not in the task\'s kernel stack, or in any of the relevant per-cpu exception stacks. This can happen when the number of NT_PRSTATUS notes does not match the number of online cpus. Without the patch, the command may generate a segmentation violation, fail with the error message \"bt: cannot determine starting stack pointer\", or fail with an error message indicating that the command \"cannot transition\" from an exception stack to the previous stack. (andersonAATTredhat.com)- Fix for the X86_64 \"bt\" command for displaying the backtraces of active tasks running on the non-crashing cpus in kdump dumpfiles in which the \"crash_nmi_callback\" function frame does not appear in the per-cpu NMI exception stacks. That function frame is normally used as the starting point for the backtraces of those tasks, but if it does not exist, the \"notify_die\" frame will be used instead. Without the patch, the backtraces of the active non-crashing tasks are incorrect or incomplete. (andersonAATTredhat.com)- Increment the X86_64 NR_CPUS maximum value from 5120 to 8192 to be able to account for Linux 3.13-rc1 and later kernels in which CONFIG_MAXSMP has been configured. If that is true, the CONFIG_NR_CPUS value is overridden, and the kernel NR_CPUS value will be set to 8192. This will cause the crash session to fail with the messages \"WARNING: kernel-configured NR_CPUS (8192) greater than compiled-in NR_CPUS (5120)\" and \"crash: recompile crash with larger NR_CPUS\". (andersonAATTredhat.com)- A crash-7.0.3 fix for the proper determination of the kernel NR_CPUS configurable for Linux 3.8 and later kernels introduced a regression in Linux 3.8 and later kernels if: (1) the kernel is configured with CONFIG_SLAB, and (2) the sum of the kernel\'s NR_CPUS and MAX_NUMNODES values exceed the NR_CPUS value compiled into the crash utility. Without the patch, the crash session generates a segmentation fault while it indicates \"please wait: gathering kmem slab cache data\". (andersonAATTredhat.com)- Update for the extensions/trace.c extension module to support the ftrace data structure changes introduced in Linux 3.10 kernels. Without the patch, loading the module with the \"extend\" command fails with the error message \"extend: trace.so: no commands registered: shared object unloaded\". (d.hatayamaAATTjp.fujitsu.com)- Increment the S390 and S390X NR_CPUS maximum value from 64 to 512. (holzheuAATTlinux.vnet.ibm.com)- Implemented support for the redesigned per-slab object bookkeeping that was introduced in Linux 3.13-rc1 for kernels configured with CONFIG_SLAB. In those kernels, the head page structure associated with each slab is overloaded to serve as the (now removed) slab data structure, and the array of kmem_bufctl_t data structures that used to be appended to each slab data structure for object management has been replaced by a new freelist stack mechanism. Without the patch, the crash session would fail during initialization with the error message \"crash: invalid structure member offset: kmem_cache_s_c_num\". It should be noted that this patch has only been tested on 3.13-rc1 kernels, which do not have the modified freelist_idx_t in place as of yet, so the replacement of integer-sized indexes with byte or short sized indexes had not been checked in. Furthermore, if this proposed patch set gets accepted: [RFC][PATCH 0/3] re-shrink \'struct page\' when SLUB is on. https://lkml.org/lkml/2013/12/11/589 then both CONFIG_SLAB and CONFIG_SLUB support in the crash utility will be broken yet again. (andersonAATTredhat.com)- In order to facilitate the building of the crash binary with either or both of the optional LZO or SNAPPY compression libraries, two new Makefile targets have been added: $ make lzo $ make snappy Without the patch, the CFLAGS.extra and LDFLAGS.extra files must be created or modified as described in these changelog entries: http://people.redhat.com/anderson/crash.changelog.html#LZO http://people.redhat.com/anderson/crash.changelog.html#SNAPPY This patch simply does the work automatically. After having done it one time, there is no need to use the targets for subsequent builds. The relevant libraries must pre-exist on the build machine. (andersonAATTredhat.com)- Long overdue update of the README file. (andersonAATTredhat.com)
* Tue Dec 10 2013 dvaleevAATTsuse.com- enable ppc64le
* Fri Dec 06 2013 ptesarikAATTsuse.cz- crash-compressed-booted-kernel.patch: Fix a bug that may cause removal of the booted kernel\'s vmlinux image (bnc#828260).
* Thu Nov 21 2013 dmairAATTsuse.com- Implementation of 7.0.3 from upstream and patch refresh.- Fix for the ARM architecture if the backtrace unwind information cannot be gathered during session initialization. Without the patch, the two unwind-related warning messages indicating \"WARNING: UNWIND: failed to gather unwind_table list\" and \"WARNING: UNWIND: failed to initialize module unwind tables\" are followed by the fatal error message \"crash: cannot hash task_struct entries\". (andersonAATTredhat.com)- Fix for the \"help -[Dn]\" dumpfile information display of the GUID EFI table in the header of SADUMP dumpfiles. Without the patch, only 33 of the 36 bytes in the table are translated. (d.hatayamaAATTjp.fujitsu.com)- Fix for the determination of the kernel NR_CPUS configurable for Linux 3.8 and later kernels that are configured with CONFIG_SLAB. Without the patch, the kernel\'s compiled-in NR_CPUS value was incorrectly calculated to be the sum of the kernel\'s NR_CPUS and MAX_NUMNODES configurables. (andersonAATTredhat.com)- In the next release of makedumpfile, the status field of the dumpfile header of compressed kdumps will show the compression type that was utilized. The \"help -[Dn]\" output has been updated to display that information. (andersonAATTredhat.com)- For kernels configured with CONFIG_SLAB in which an array_cache pointer referenced by a kmem_cache structure is invalid, the individual cache(s) will be marked as invalid. During session initialization, the message \"crash: kmem_cache: : invalid array_cache pointer\" will be displayed, and during runtime, attempts to access the cache(s) will result in a message indicating that the cache is \"[INVALID/CORRPUTED]\". Without the patch, the message \"crash: unable to initialize kmem slab cache subsystem\" is displayed during session initialization, and run-time commands that attempt to access the kmem slab cache subsystem fail with the error message \"kmem cache slab subsystem not available\". (andersonAATTredhat.com)- Fix for the \"kmem -[sS] \" option in Linux 3.6 and later kernels configured with CONFIG_SLAB. Without the patch, the command fails with the message \"kmem: address is not allocated in slab subsystem: . This also causes the \"kmem \" command to (quietly) fail to determine that the address is a slab object. (andersonAATTredhat.com)- Fix for the \"bt\" command if a kernel __init text address is encountered. Without the patch, and depending upon the reallocation of the __init text memory, a bogus framesize may be calculated, or more likely, in a compressed kdump, a warning message indicating \"bt: page excluded: kernel virtual address:
type: gdb_readmem_callback\" will be displayed following the frame data. (andersonAATTredhat.com)- Update for determining whether an S390X PTE contains a swap entry in Linux 3.12 and later kernels. (holzheuAATTlinux.vnet.ibm.com)- Resurrected the translation and display of the page.flags bits by the \"kmem -p\" command on Linux 2.6.26 and later kernels whose vmlinux debuginfo data contains either the \"pageflags\" enumerator or the \"pageflag_names\" array of trace_print_flags structures. If they are not available, just the page.flags value is printed in hexadecimal, as has been done since Linux 2.4.9. (andersonAATTredhat.com)- Fix for the \"bt\" command when used with vmcore files that were created with the recently-introduced \"virsh dump --memory-only\", which dumps KVM guests into an ELF vmcore similar to those created by the kdump facility. Without the patch, a faulty backtrace for the panic task may be generated due to the use of incorrect starting RSP/RIP registers; this happens because (unlike kdump) the non-panicking cpus are offlined prior to the dumpfile being created, which in turn leads to the use of the wrong NT_PRSTATUS note. (andersonAATTredhat.com)- Fix for the CPU number display on systems with 255 or more cpus during the initial banner, by the \"set\" command, the \"ps\" command, and by all commands that display the per-task header consisting of the task address, pid, cpu and command name. Without the patch, for cpu 255, the \"sys\" command displays \"NO_PROC_ID\", and the other commands would show a \"-\" for the cpu number; for cpu numbers greater than 255, garbage values would be displayed in the cpu number field. (andersonAATTredhat.com)- Implemented support for compressed kdump header version 6, in which makedumpfile(8) adds new fields in the kdump_sub_header to support large memory systems with pfn values that are larger than 32-bits. Without the patch, if the system contains physical memory located in high memory such that its maximum pfn value is overflows the 32-bit \"max_mapnr\" field in the header, the crash session will fail with the error message \"crash: vmlinux and vmcore do not match!\". (jingbai.maAATThp.com)- Fix for the \"net -s\" command on Linux 3.8 and later kernels. Without the patch, the command fails with the message \"net: invalid structure member offset: inet_opt_daddr\". (andersonAATTredhat.com)- Fix a build failure in a native ARM64 environment due to obsolete LKCD dumpfile headers. (andersonAATTredhat.com)- Implementation of a new \"per-cpu object\" as an argument format that can be passed to the \"p\", \"struct\", \"union\" or \"
*\" commands. The format is expressed as either : or as :, where the per-cpu symbol or per-cpu offset must precede a colon, and where the follows the colon. The cpu-identifier may be expressed in any of the following manners: : CPU of the currently selected task. :a[ll] all CPUs. :#[-#][,...] CPU list(s), e.g. \"1,3,5\", \"1-3\", or \"1,3,5-7,10\". Without the patch, per-cpu symbols are only accepted by the \"p\" command, and the data type and the resolved kernel virtual address for each per-cpu instance are displayed shown. With this patch, a colon and a cpu-specifier may be appended to the symbol name, and the the contents of the symbol on each cpu that is specified will be displayed by the \"p\" command. For the \"struct/union/
*\" commands, an argument may be specified using either a per-cpu offset value or per-cpu symbol name followed by a colon and cpu-specifier, and the contents of each structure/union on each specified cpu will be displayed. (ptesarikAATTsuse.cz) Fixed several minor flaws that were detected by a Coverity Scan: tools.c: 992:warning[invalidScanfArgType_int] – %d in format string (no. 1) requires \'int
*\' but the argument type is \'unsigned int
*\'. memory.c: 7461:error[uninitvar] – Uninitialized variable: page_cache_size filesys.c: 731:error[resourceLeak] – Resource leak: version kernel.c: 5675:error[uninitvar] – Uninitialized variable: action 7799:error[memleakOnRealloc] – Common realloc mistake: \'ikconfig_all\' nulled but not freed upon failure configure.c: 793:error[mismatchAllocDealloc] – Mismatching allocation and deallocation: fp remote.c: 1120:error[resourceLeak] – Resource leak: pipe va_server.c: 316:error[memleak] – Memory leak: disk_hdr va_server_v1.c: 311:error[memleak] – Memory leak: disk_hdr makedumpfile.c: 80:error[memleakOnRealloc] – Common realloc mistake: \'ptr\' nulled but not freed upon failure sadump.c: 231:error[memleakOnRealloc] – Common realloc mistake: \'sdh\' nulled but not freed upon failure extensions/snap.c: 550:error[uninitvar] – Uninitialized variable: prstatus_len 541:error[uninitvar] – Uninitialized variable: l_offset extensions/trace.c: 1477:error[resourceLeak] – Resource leak: file (andersonAATTredhat.com)
* Fri Sep 13 2013 ptesarikAATTsuse.com- crash-crosscrash-hint.diff: Removed, because crosscrash isn\'t maintained any longer.
* Thu Sep 12 2013 dmairAATTsuse.com- Implementation of v7.0.2 from upstream. o See http://people.redhat.com/anderson/crash.changelog.html for a complete list of changes from 6.1.3.- crash-rl_digit_loop-return.patch - removed- crash-missing-declarations.patch - refreshed- crash-rl_digit_loop-return.patch - refreshed- eppic-switch-to-system-lib.patch - refreshed
* Fri May 10 2013 dmairAATTsuse.com- Implementation of v6.1.3 from upstream. crash-display-date-fix.patch - removed/redundant crash-kmem_cache_slab.patch - removed/redundant crash-siginfo.patch - removed/redundant crash-var_length_log_rec.patch - removed/redundant eppic-switch-to-system-lib.patch - Implementation of EPPIC via system library rather than retrieve and include in build. Added eppic constants to spec file without removing the sial constants for now. crash-crosscrash-hint.diff - refreshed crash-make-emacs-default.diff - refreshed crash-sles9-time.patch - refreshed
* Wed Feb 27 2013 cooloAATTsuse.com- update license to new format
* Mon Feb 04 2013 dmairAATTsuse.com- Re-execution of 150764 by tabrahamAATTsuse.com to re-align patch content, re-number patches for latest spec contents and to remove some incidental content (e.g. whitespace insertion and leftover comments of new lines). Comment from tabraham follows: - added crash-display-date-fix.patch This is a backport of the fix from crash-6.0.9 to fix the date displayed by the initial system banner and by the \"sys\" command for linux kernel 3.6 and later. Without the patch, the date displayed will be that of the UNIX epoch adjusted to local time. - added crash-kmem_cache_slab.patch This is a backport of the fix from crash-6.1.0 for Linux 3.0 and later kernels that have been configured with CONFIG_SLAB and with- out CONFIG_NODES_SHIFT. Without the patch, the warning messages \"crash: nr_node_ids: symbol does not exist\" and \"crash: unable to initialize kmem slab cache subsystem\" are displayed during initialization, and the \"kmem -[sS]\" options fail with the message \"kmem: kmem cache slab subsystem not available\".
* Mon Feb 04 2013 dmairAATTsuse.com- crash-compressed-booted-kernel.patch: Fix for \"crash when invoked without arguments fails to analyze the live system\" (bnc#777516).
* Fri Jan 25 2013 tabrahamAATTsuse.com- crash-var_length_log_rec.patch: support variable-length record kernel log buffer present in kernel 3.5 and later (bnc#796151).
* Sun Jul 29 2012 ajAATTsuse.de- Fix build with glibc 2.16 (struct siginfo -> siginfo_t).
* Tue Jul 17 2012 dmairAATTsuse.com- Enabled support for reading dumpfiles compressed by LZO using makedumpfile version 1.4.4 or later.
* Fri Jun 01 2012 dmairAATTsuse.com- Update to crash 6.0.7 from upstream and adjust patches to apply without offsets. Upstream changes: o Enhanced the search command to allow the searched-for value to be entered as a crash (expression) or a kernel symbol name. The resultant value of an (expression) or kernel symbol value must fit into in the designated value size if -w or -h are used, and neither variant may be used with the -c option. If found, both the resultant value and the argument input string will be displayed next to the target address(es). o Added a new \"search -t\" option that will restrict the search to the kernel stack pages of all tasks. If one or more matches are found in a task\'s kernel stack, the output is preceded with a task-identifying header. o Fix for the s390x \"bt -[tT]\" options when run on an active task on a live system. Without the patch, the options fail with the message \"bt: invalid/stale stack pointer for this task: 0\". o Fix for s390x \"vm -p\" option, which may show invalid user to physical address translation data if a page is not mapped. Without the patch, a page\'s translation may indicate \"
SWAP: (unknown swap location) OFFSET: 0\", or show an incorrect swap offset on an actual swap device. o Added new \"vm -[xd]\" options to be used in conjunction with \"vm -[mv]\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"vm -[mv]\". The new flags may also be used with \"foreach vm -[mv]\". o Fix for the s390x \"vm -p\" and \"vtop -u \" commands if the page containing the relevant PTE is not mapped. Without the patch, the commands fail with the error message \"vm: read error: kernel virtual address: 0 type: entry\" or \"vtop: read error: kernel virtual address: 0 type: entry\" o Fix for the s390x \"vm -p\" command and \"vtop -u \" commands to properly translate pages that are swapped out into their swap file and offset. Without the patch, the swap file and offset would not be displayed. o Added new \"list -[xd]\" options to be used in conjunction with \"list -s\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"list -s\". o Added new \"net -[xd]\" options to be used in conjunction with \"net -S\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"net -S\". The new flags may also be used with \"foreach net -S\". o Added new \"mach -[xd]\" options to be used in conjunction with \"mach -c\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"mach -c\". o If the value read from the cpu online, present, or possible masks contains a cpu bit value that is outside the architecture\'s maximum NR_CPUS value, print a warning message during invocation. Without the patch, a corrupt vmcore containing a bogus mask value could quietly corrupt heap memory. o Add support to for reading dumpfiles compressed by LZO using makedumpfile version 1.4.4 or later. This feature is disabled by default. To enable this feature, build the crash utility in the following manner: (1) Install the LZO libraries by using the host system\'s package manager or by directly downloading libraries from author\'s website. The packages required are: - lzo - lzo-minilzo - lzo-devel The author\'s website is: http://www.oberhumer.com/opensource/lzo (2) Create a CFLAGS.extra file and an LDFLAGS.extra file in top-level crash sources directory: - enter -DLZO in the CFLAGS.extra file - enter -llzo2 in the LDFLAGS.extra file. (3) Build crash with \"make\" as always.
* Only available as a source option for manual build in this environment o Fix for the included \"trace\" extension module. Without the patch, if the module initialization sequence fails, a double-free in the module may lead to a subsequent malloc() segmentation violation in the crash session. o Incorporated the \"ipcs\" extension module written by Qiao Nuohan as a built-in command. The command displays the kernel\'s usage of the System V shared memory, semaphore and message queue IPC facilities. It differs from the original extension module by fixing a failure scenario if the current task is exiting, and adds a \"-n pid|task\" option, which displays the IPCS facilities with respect to the namespace of a given pid or task. o Fix for a gdb-7.3.1 regression that causes the line number capability to fail with certain ranges of x86 base kernel text addresses. Without the patch, the \"dis -l \" or \"sym \" commands would fail to show line number information for certain ranges of base kernel text addresses. o Added a new \"printm\" command to the embedded gdb module. It is currently only used by the \"pstruct\" extension module, but can be used to dump the type, size, offset, bitpos and bitsize values of an expression. o Added a new \"runq -t\" option that displays the timestamp information of each cpu\'s runqueue, which consists of either the rq.clock, the rq.most_recent_timestamp or rq.timestamp_last_tick value, whichever applies. Following each cpu timestamp is the last_run or timestamp value of the active task on that cpu, whichever applies, along with the task identification. o Fix for an initialization-time warning when running on a live system with the most recent version of the modprobe command, which no longer supports the -l and --type options. The modprobe is used to detect whether the crash.ko memory driver is part of the distribution. Without the patch, a warning message is issued that indicates \"/sbin/modprobe: invalid option -- \'l\'\". If the driver is built into the kernel, the message is harmless. If the driver is not built into kernel, then the crash.ko (/dev/crash) driver would not be selected as the live memory source.
* Thu May 17 2012 ptesarikAATTsuse.cz- delete crash-foreach-match-running.patch: upstream
* Mon May 14 2012 dmairAATTsuse.com- Update to crash 6.0.6 from upstream o Extend the supported cross-architecture build capability so that it applies to the SIAL extentension module. Without the patch, when building the SIAL module an environment where the overlying crash utility was built with \"make target=ARM\", \"make target=PPC\", or \"make target=X86\", the SIAL extension module would continue to be built for the host architecture o Fixes for memory leaks and possible segmentation violations when unloading SIAL extension module scripts. o Fix for the new \"foreach RU\" task state qualifier. Without the patch, the runnable tasks are not selected. o Fix to disallow multiple task states from being entered using the \"foreach \" qualifier. Without the patch, if multiple states were entered, the last one on the command line would be honored. o Fix for the \"extend\" command to allow the usage of 32-bit PPC extension modules. Without the patch, the command fails with the message: \"extend: .so: not an ELF format object file\". o If an input line starts with \"#\" or \"//\", then the line will be saved as a comment that is visible when re-cycling through the command history list. o Fix for a crash-5.1.9 regression that broke the \"bt -g\" option. Without the patch, the option is ignored completely. o Fix for s390x virtual-to-physical translation of virtual addresses that are backed by 1MB pages. o The s390x has a dumpfile method that creates \"live dumps\", where the kernel continues to run while the dumpfile is being created. The initial system banner display and the \"sys\" command will inform the user that the dumpfile is a \"[LIVE DUMP]\", and the \"bt -a\" option will fail with the message \"bt: -a option not supported on a live system or live dump\". o Newly-created dumpfiles generated by the \"snap.c\" extension module will now be recognized as \"live dumps\". Accordingly, the initial system banner display and the \"sys\" command will inform the user that the dumpfile is a \"[LIVE DUMP]\", and the \"bt -a\" option will fail with the message \"bt: -a option not supported on a live system or live dump\". o If \"bt\" alone is attempted on an active task in a \"live dump\", it will indicate \"(active)\", i.e., the same as if it were attempted on a live system. o If an extension module does not define the appropriate architecture, i.e., \"-DX86\", \"-DX86_64\", etc., then the inclusion of \"defs.h\" will generate a compiler failure indicating \"error: \'NR_CPUS\' undeclared here (not in a function)\". In that case, the architecture will now default to that of the host machine. o Prevent a highly-unlikely incorrect calculation of the maximum cpudata array length of a kmem_cache during initialization of of CONFIG_SLAB kernels. o Prevent an infinite loop during the initialization of the kmem_cache subsystem in CONFIG_SLAB kernels if the cache list or the vmcore is corrupt. If the kmem_cache list links back into itself, messages showing the first \"duplicate\" entry in the list and \"crash: unable to initialize kmem slab cache subsystem\" will be displayed. o Update to the \"mod\" command to additionally search for module object files in the directory containing the kernel namelist (vmlinux) file. This will allow an alternate module-debuginfo directory tree to be set up like so: [#] cd [#] rpm2cpio kernel-debuginfo-.rpm | cpio -idv Having done that, and by referencing the vmlinux file in that directory tree directly or by symbolic link, the \"mod\" command will search for module object files starting from the directory containing the vmlinux file if they are not found in the standard /lib/modules/ directory. o Update to the s390x \"bt\" command if a task was running in userspace. Without the patch, the back trace display ended at the kernel entry function frame; with the patch, the user space PSW register is displayed with a \"(user space)\" tag, followed by the general purpose register set. o In the unlikely event that the access of ARM or x86_64 kernel unwind table data fails during crash invocation, print a warning message and allow the crash session to continue. Without the patch, the crash session would fail immediately.
* Tue Mar 27 2012 dmairAATTsuse.com- Update to crash 6.0.5 from upstream and adjust patch positions to match current crash source. 6.0.5 changelog is: o Enhancement to the \"foreach\" command to allow any of the \"name\" arguments to be POSIX extended regular expressions. The expression string must be encompassed by \"\'\" characters, and will be matched against the names of all tasks. o Fix for the embedded gdb module\'s \"ptype\" command, and by extension, the crash utility\'s \"struct\" command, to be able to fully display embedded structure or union members of a structure/union. Without the patch, if a structure or union is a member of a structure or union that is a member of a structure or union, then it is displayed as \"struct {...}\" or \"union {...}\". o Extend the \"ps -l\" output to also display the task state next to its last_run/timestamp value. o Enhancement to the \"foreach\" command which adds a new \"state\" task-indentifier argument that filters tasks by their task state. The state argument may be any of the task states displayed by the \"ps\" command: RU, IN, UN, ST, ZO, SW or DE. o Implemented a new pc->cmd_cleanup function pointer and an optional pc->cmd_cleanup_arg argument that will allow any command to register a function and an optional argument that will be called after a command has completed successfully, or more likely, unsuccessfully. Normally the only cleanup required for a command is the freeing of buffers that were allocated with GETBUF(), but that is performed automatically after each command is run. However, with the introduction of the new POSIX regular expression functionality of the \"foreach\" command, there needed to be a way to call regfree() in the case where where regcomp() was called successfully, but then the command later encountered one of several fatal error conditions. This facility is also available for use by extension module commands. o Enforce the usage of a kernel thread\'s pgd from its active_mm for the ARM \"vtop -c\" command; if its active_mm is NULL, make the command fail similarly to the other architectures, displaying the error message \"vtop: no active_mm for this kernel thread\". o Fix for the x86_64 \"bt\" command running against recent kernels if an active task was operating on its IRQ stack when the crash occurred. Without the patch, the determination of the IRQ exception frame was off-by-8, displaying invalid register data and the error message \"bt: WARNING: possibly bogus exception frame\". o Update to handle the vfsmount structure change in 3.3 kernels, in which most members of the vfsmount structure have been moved into a new \"struct mount\", and the vfsmount structure has been embedded in the new mount structure. Without the patch, the following commands will fail, displaying the following error messages: mount: \"mount: invalid structure member offset: vfsmount_mnt_list\" files: \"files: invalid structure member offset: dentry_d_covers\" vm: \"vm: invalid structure member offset: dentry_d_covers\" swap: \"swap: invalid structure member offset: dentry_d_covers fuser: \"files: invalid structure member offset: dentry_d_covers\" The \"fuser\" command generates the above error because it uses the \"files\" command behind the scenes. o Fix for the \"ps\" command to prevent the display of \"??\" under the ST (task state) column. Without the patch, in more recent kernels, if more than one bit were set in the task_struct.state field, the state would display \"??\". With the fix, the primary state will always be displayed. o Update to the output of the \"set\" command when it displays a task\'s state. Without the patch, if more than one bit was set in the task_struct.state field, \"STATE: (unknown)\" would be displayed. With the fix, all bits in both the task_struct.state and task_struct.exit_state fields are translated. o Implemented a new \"vm -P \" option, which is similar to \"vm -p\", but only does the page translations of the specified VM area of a context. o Add support for the Freescale PowerPC e500mc version of the E500 processor chipset, and rework the PPC platform-specific code in order to more easily support new processors. o Implemented a new \"gdb\" crash environment variable that can be used to alter a crash session\'s behavior such that all commands are passed directly to the embedded gdb module. The new mode is turned on and off by entering \"set gdb on\" and \"set gdb off\". When running in this mode, the command prompt will be \"gdb>\". In order to execute native crash commands while running in this mode, precede the command with the \"crash\" directive, for example, \"crash ps\". o Fix for a \"
*
*
* stack smashing detected
*
*
*: crash terminated\" failure during the initial system banner display on a 32-bit PPC platform. o Redesigned/simplified the internal read_string() function to prevent a potential segmentation violation. o Updates for the 32-bit PPC \"vtop\" command output: (1) Translate kernel virtual addresses for FSL BOOKE by using the TLBCAM setting (2) Remove the PMD line from the display (3) Fix the displayed PHYSICAL values of FSL BOOKE PTE format o Fix for crash invocation failure on 3.3-era kernels in which the former standalone \"xtime\" timespec structure has been moved into the \"timekeeper\" structure. Without the patch, the crash session would fail early on with the message \"crash: cannot resolve: xtime\". The patch also prevents the crash session failure in the unlikely event that the timespec access fails.
* Wed Feb 29 2012 dmairAATTsuse.com- Update to crash 6.0.4 from upstream and adjust patch locations to match current crash source. 6.0.4 changelog is: o Fix to allow the recently-added \"mod -g\" and \"mod -r\" options to be used together. o Additional update for 3.1.x and later kernels configured with CONFIG_SLAB, which have replaced the kmem_cache.nodelists[] array with a pointer to an outside array. o Document the \"crash [-h|--help] all\" option in the crash.8 man page and in the \"crash [-h|--help]\" output. o Fix the S390/S390X-specific \"s390dbf\" command\'s \"hex_ascii\" debug data printing routine to prevent the display of non-ASCII characters. o Fix for ARM stack unwinding on 3.2 and later kernels due to commit: http://git.kernel.org/linus/de66a979012dbc66b1ec0125795a3f79ee667b8a o Implemented a new \"search -x \" option that displays the memory contents before and after any found search target. o Fix for the x86_64 Xen hypervisor \"bt\" command. Without the patch, the contents of the RDX register in exception frames incorrectly shows the contents of the RCX register. o Implementation of a platform-based vmalloc address translation scheme for the 32-bit PPC architecture, introducing suppport for the PPC44X platform while maintaining the current default platform. o Fix for the usage of native gdb commands where the command output is redirected to a pipe and then redirected to a file. o Fix to prevent a crash session that is run over a network connection that is killed/removed from going into 100% cpu-time loop. o Fix for the support of PPC64 compressed kdumps, a regression that was introduced in crash-6.0.3 when support for 32-bit PPC compressed kdumps was implemented. o Fix for the x86_64 \"bt\" command to prevent the possible skipping of the stack frame just above an exception frame that indicates \"[exception RIP: unknown or invalid address]\". Patches with modified target locations are: crash-make-emacs-default.diff crash-sles9-time.patch crash-crosscrash-hint.diff crash-missing-declarations.patch
* Tue Feb 07 2012 dmairAATTsuse.com- Update to crash 6.0.3 from upstream and modifications to compile. 6.0.3 change log is: o Fix to gdb-7.3.1/bfd/bfdio.c to properly zero out a complete struct stat with a corrected memset argument o Fix for the SIAL extension module to remove a call to sial_free() for an uninitialised variable o Fix for the \"runq\" command for kernels that are configured with CONFIG_FAIR_GROUP_SCHED o Implemented build and code for the analysis of 32-bit PPC ELF kdump vmcores o Implemented the capability of building a PPC crash binary on a PPC64 host, which can be done by entering \"make target=PPC\" o Determine the PPC page size from the kdump PAGESIZE vmcoreinfo data o Fix for the \"kmem -[sS]\", \"kmem -[fF]\" and \"kmem
\" options in 3.2 kernels o Addition of a set of dumpfile read diagnostic debug statements o Fix for X86 kernels that have CONFIG_X86_32, CONFIG_DISCONTIGMEM, CONFIG_DISCONTIGMEM_MANUAL and CONFIG_NUMA all configured o Fix for the \"vtop\" command on large NUMA X86 kernels where a node\'s starting physical address is larger than 32-bits o Update for the ARM architecture to recognize a recent change of its vmlinux section name from \".init\" to \".init.text\" o Significant speed increase of the \"kmem -p\" command, especially on large-memory systems o Implemented new \"irq -a\" and \"irq -s\" options o Removal of a redundant read of the kernel\'s __per_cpu_offset pointers in the ARM architecture\'s arm_get_crash_notes() function o Fix for an ARM architecture segmentation violation because of a stack overflow due to recursion in the page table translation code o Fix for the the \"FREE HIGH\" tally in the X86 \"kmem -i\" display o Fix for the \"kmem -n\" output display for 32-bit architectures that are configured with CONFIG_SPARSEMEM o Cleanup of several SIAL extension module files to address bison 2.5 and gcc 4.4.3 compile-time warnings o Fix for \"net -[sS]\" command options on the ARM architecture o Fix for the ARM \"bt\" command to allow the core kernel unwind tables to be used in cases where the module unwind tables are inaccessible o Implementation of a new \"dev -d\" option that displays disk device I/O statistics o Update for 3.1.x and later kernels configured with CONFIG_SLAB, which have replaced the kmem_cache.nodelists[] array with a pointer to an outside array o Implemented build and code for analysis of 32-bit PPC compressed kdump vmcores o Prevent the \"runq\" command from dumping an unending loop of tasks if the CFS runqueue has been corrupted o Repurposed/renamed the rarely-used and rarely-needed \"mod -r\" option to \"mod -R\" o Implemented a new \"mod -r\" option, which will pass the \"-readnow\" flag to the embedded gdb module, which will override the two-stage strategy that it uses for reading symbol tables from module object files o Performance increase for the \"kmem -s
\" option on kernels configured with CONFIG_SLAB, most notably on kernels whose kmem_cache.array[NR_CPUS] array is several pages in size o Require that the \"\" argument to \"kmem -s \" be escaped with a \'\\\' character in two situations: (1) in the highly-unlikely case of a kmem_cache slab named \"list\", to prevent the ambiguity with the \"kmem -s list\" command option. (2) if the first character of the actually is a \'\\\' character Modifications to compile are as follows: o Replacement of crash-6.0.2.tar.gz with crash-6.0.3.tar.gz o Remove crash-wrong-memset.patch the fix is present in 6.0.3 o Remove crash-add-read-diags.patch the change is in 6.0.3
* Mon Jan 09 2012 ptesarikAATTsuse.cz- crash-wrong-memset.patch: fix compilation on SLE11.
* Thu Jan 05 2012 dmairAATTsuse.com- Update to crash 6.0.2 from upstream and modifications to compile.
* Tue Dec 27 2011 idonmezAATTsuse.com- Fix wrong size parameter in memset call
* Mon Nov 07 2011 dmairAATTsuse.com- Update to crash 6.0.0 from upstream and modifications to compile.
* Thu Oct 13 2011 ptesarikAATTsuse.cz- crash-debuginfo-compressed.patch: Search debuginfo files in the same directory as the original gzipped kernel image (bnc#723639).
* Tue Oct 11 2011 ptesarikAATTsuse.cz- Add Requires: kernel-$flavor to new-style KMP packages.- Provide old-styl crash-kmp (for SLES9).
* Mon Oct 10 2011 ptesarikAATTsuse.cz- Build the crash memory driver kernel module as a KMP.
* Mon Oct 10 2011 ptesarikAATTsuse.cz- Change the license from GPLv3 (only) to GPLv3 or higher.
* Thu Sep 22 2011 lchiquittoAATTsuse.com- Add the gcore extension as a subpackage for i386 and x86_64. This extension can be used to create a core dump file of a user-space task that was running in a kernel dumpfile.
* Fri Jun 10 2011 ptesarikAATTsuse.de- Put correct licenses in the RPM header.
* Fri Jun 10 2011 ptesarikAATTsuse.de- crash-missing-declarations.patch: re-apply the patch, because this is still not fixed upstreams and still breaks ppc64 builds.
* Thu Jun 09 2011 ptesarikAATTsuse.de- Update to 5.1.6 o add \"kmem -o\" option (each CPU\'s per-cpu offset value) o remove obsolete \"kmem [-[l|L][a|i]]\" options from the kmem help page o add \"kmem -g [flags]\" option to display the enumerator value of bits in the page structure\'s \"flags\" field o add \"rd -a\" option to display printable ASCII data only o add \"rd -N\" option to use network byte order o extend \"mach\" to display the size and address of each per-cpu IRQ stack and per-cpu exception stack, if they exist o extend \"kmem
\" to display module name if appropriate o arm: support CONFIG_SPARSEMEM o fixes to enable Linux 3.x numbering o x86: fix \"search -k\" if the first memmap page struct does not map to physical address 0 o fix \"search -k\" for kernels with multiple non-sequential NUMA nodes, memory holes between them and no memmap page structures refering to the holes o fix \"kmem -s
\" for addresses in a non-first page of a compound slab and kernels compiled with CONFIG_SLUB and CONFIG_PAGEFLAGS_EXTENDED o fix NR_SECTION_ROOTS to ensure a non-zero value o arm: fix a potential double free in read_module_unwind_table() o fix compiler warnings when building with \"make warn\" o fix several typos in the crash(8) man page o see http://people.redhat.com/anderson/crash.changelog.html for the complete changelog- drop crash-xen-x86_64-increase-max-vcpus.patch: superseded by mainline\'s allocating VCPU structures dynamically- refresh all patches- specfile cleanups
* Wed May 25 2011 idonmezAATTnovell.com- Update to 5.1.5, mainly gcc 4.6 and kernel 2.6.39 fixes, see http://people.redhat.com/anderson/crash.changelog.html for complete changelog.- Refresh crash-sles9-time.patch- Dropped the following patches applied upstream:
* crash-compressed-booted-kernel
* crash-compressed-kernel
* crash-missing-declarations.patch
* crash-xen-domain_vcpu.patch
* crash-xen-opt_sched.patch
* crash-xen-per_cpu-init_tss.patch
* crash-xen-per_cpu_shift.patch
* crash-xen_virt_start.patch
* Fri Jan 07 2011 ptesarikAATTnovell.com- crash-xen-per_cpu-init_tss.patch: init_tss is a per-cpu variable in Xen-4.0.0 (bnc#612128).- crash-xen-x86_64-increase-max-vcpus.patch: x86_64 can have up to 8192 virtual CPUs with Xen-4.0.0 (bnc#612128).- crash-xen-domain_vcpu.patch: Xen-4.0.0. vcpu array is no longer embedded in struct domain (bnc#612128).- crash-xen-opt_sched.patch: opt_sched is __initdata in Xen-4.0.0, so it\'s value is not available in the crash dump. Use opt as a replacement (bnc#612128).- crash-xen_virt_start.patch: account for the changed value of XEN_VIRT_START in Xen-4.0.0 (bnc#612128).- crash-xen-per_cpu_shift.patch: correctly determine PERCPU_SHIFT for Xen syms (bnc#612128).
* Mon Jan 03 2011 dmairAATTnovell.com- Update to 5.1.1 o Fix for the potential to miss tasks when walking the pid_hash table in 2.6.24 and later kernels. Without the patch, the task will simply not be seen in the gathered task list. o Enhancement for the ARM architecture\'s \"bt\" command to print out the user space register set for tasks entering the kernel via the syscall entry point. o Rework of the handling of \"set\" commands that are put in .crashrc files so that only the following options are resolved prior to session initialization: silent, console, core, edit, namelist, and zero_excluded. All others are resolved immediately after session initialization is complete. Accordingly, the use of \"set -c \", \"set -p\", \"set -a [task|pid]\" and set [pid|task]\" are now acceptable .crashrc commands. o The entering of \"set -v\" in a .crashrc file would cause an immediate segmentation violation. The \"set\" command rework above defers the command until session initialization is complete. o The entering of \"set dumpfile \" in a .crashrc file would cause a fatal \"seek\" error during session initalization with most most dumpfile types, so the \"dumpfile\" option has been removed from the \"set\" command. o The execution of \"alias\" commands from a .crashrc file used to be performed immediately; that behavior has been changed so that they are executed immediately after session initialization is complete. o Enhancement of the \"repeat\" command to allow command aliases. o Fix for running \"kmem -s\" on a live system if an offline cpu is brought back online while the command is executing. Without the patch, the online operation may cause a segmentation violation. o Change the behavior of \"bt -[tT]\" to allow the command options to be run on active tasks on live systems. Without the patch, both command options would display the task data banner followed by \"(active)\". o Fix for the ARM architecuture\'s \"irq\" command when run on 2.6.36 and later kernels. Without the patch, the command fails with the error message \"irq: invalid kernel virtual address: 23 type: irq_chip typename\". The fix replaces the custom ARM IRQ dumping function with the architecture-neutral version. o Introduced support for using /proc/kcore as an alternative source of live memory to /dev/mem. Doing so allows vmalloc memory access on 32-bit architectures when the underlying mapped physical memory is in highmem, which is not allowed by the /dev/mem driver. It would also be usable on systems that are configured with CONFIG_STRICT_DEVMEM but still configured with CONFIG_PROC_KCORE. To enforce the use of /proc/kcore, it may be entered on the command line. o If a live crash session attempts to use /dev/mem as a live memory source, and it is determined that the system is configured with CONFIG_STRICT_DEVMEM, /proc/kcore will automatically be tried as an alternative. o Fix to allow \"/dev/crash\" to be entered on the command line for live sessions. Because it is used automatically if it exists, it is never necessary to enter it on the command line. However, if it is used, without the patch, the session fails during initializaion with the error message \"crash: /dev/crash: No such file or directory\" if the crash.ko driver is a module, or \"crash: /dev/crash: not a supported file format\" if the driver is built into the kernel. o Fix for the ARM \"bt\" command to address the issue behind faulty warning messages that indicate \"WARNING: UNWIND: unsupported personality routine\". o Fix for the ARM \"bt\" command to address the issue behind faulty warning messages that indicate \"bt: WARNING: UNWIND: cannot find index for
\".
* Mon Dec 13 2010 dmairAATTnovell.com- Update to 5.1.0 o x86: Fix for the \"bt\" command for active, non-chrashing, tasks on 2.6.31 and later kernels without CONFIG_4KSTACKS. o x86 and x86_64: Add module names to \"bt\" outputs. o Enhance the \"sym\" command to display the containing module name in brackets. o Support module per-cpu symbols after they are loaded with the \"mod -[sS]\" command. o x86: Fix for the \"bt\" command to properly handle a NMI-interrupted idle task running in cpu_idle(). o s390x: Support for compressed kdump dumpfiles created by the makedumpfile facility. o x86 Xen guest: Fix for the \"bt\" command where a vcpu received a shutdown NMI while running in the event_check_interrupt() interrupt handler. o x86 Xen guest: Fix for the \"bt\" command where a vcpu received a shutdown NMI while running in the hypercall entry point. o s390x: Fix for the \"help -n\" output on ELF vmcore dumpfiles to recognize the several architecture specific n_types. o s390x Fix for the \"help -n\" output on ELF vmcore dumpfiles to properly dump the contents of the descriptor data of each Elf64_Nhdr note. o Fix for the \"help -n\" output for diskdump and compressed kdump files to show the filename as stored in the per-file diskdump_data structure. o Resurrection of the \"irq -b\" command option for 2.6 kernels. o Fix for displaying data generated from shell-escaped commands when the data contains a \"%\" character followed by a conversion character o Re-worked the do_radix_tree() utility function to work without depending upon a hardwired copy of the kernel\'s radix_tree_node structure, and changed various RADIX_TREE values into dynamically calculated values. o Call FREEBUF() on a GETBUF()-generated buffer ub the do_radix_tree() utility function. o x86_64: Store the .debug_frame section offset and size from the vmlinux file and use its data as an alternative to the .eh_frame section data. o Fix for errors or nonsensical output from the \"irq\" command when run on 2.6.29 kernels. o Fix for error output from the \"irq\" command when run on 2.6.34 and later kernels.
* Mon Oct 11 2010 ptesarikAATTnovell.com- Update to 5.0.8 o x86_64: Fix the \"bt\" command on 2.6.30 and later kernels when using a System.map file. o Fix KVM error messages generated by store_mapfile_offset() and and load_mapfile_offset() when an invalid physical address is issued. o Fix the \"sig\" command on 2.6.35 and later kernels. o Fix the \"net -s\" command option on 2.6.33 and later kernels. o Fix the \"mod\" command on 2.6.35 and later kernels. o Fix the \"mount -f\" command on 2.6.36 and later kernels. o Fix missing \"/dev\" prefix for files in the /dev directory listed by the \"files\" command. o x86_64: Use cpu_present_map instead of cpu_online_map to determine the CPU count. o x86_64: Fix the \"bt\" command on 2.6.27 and later kernels to prevent the possible display of an invalid \"vgettimeofday\" frame above the topmost \"system_call_fastpath\" frame. o s390x: Read pointers above 4GiB correctly with the \"s390dbf\" command. o Allow building crash as an x86 binary for ARM dumpfiles on an x86_64 host. o Simplify the ARM build procedure after an initial ARM build has been completed in a crash source tree. o Allow building crash as an x86 binary on an x86_64 host. o Fix a regression in get_text_init_space() due to logic added by the ARM processor support. o SMP support SMP for the ARM architecture. o x86_64: Fix the \"bt\" command on 2.6.31 and later kernels to display the the exception frame from the forced oops after issuing an \"echo c > /proc/sysrq-trigger\". o Recognize module \"init\" symbols that are still valid.
* Mon Sep 20 2010 ptesarikAATTnovell.com- Update to 5.0.7 o ARM processor support. o Support KVM dumpfiles that have \"ram\" device header sections with a version_id of 4. o Support KVM dumpfiles from guests that were provisioned with more than 3.5GB of RAM. o Minor fix to memory.c to address a compiler warning. o \"mount\": Fix a segmentation violation if the \"init\" task (PID 1) does not exist. o x86_64: Show \"RT\" in exception stack name strings on realtime (CONFIG_PREEMPT_RT) kernels, because RT kernels may use the same per-cpu stack for different exception types. o Show tasks that could be missed in 2.6.23 and earlier kernels. o Fix the incorrect presumption that the kernel\'s task_state_array[] is NULL terminated.
* Mon Sep 20 2010 ptesarikAATTnovell.com- Update to 5.0.6 o x86_64: Fix 2.6.27 and later xendump and Xen kdump dumpfiles (\"missing end_pfn\") o Allow redirecting the output of \"s390dbf\" to a pipe. o x86: Improve the backtrace end detection algorithm in \"bt\" for tasks entering the kernel from user-space. o Warn about machine type mismatch when attempting to use a ppc64 vmlinux file on a non-ppc64 64-bit host. o x86_64: Fix the \"bt\" command if the kdump-generated NMI interrupts a multi-threaded task that has just entered kernel space and has not changed the user-space RSP register. o Allow changing internal variables in --minimal mode with the \"set\" command. o x86: Fix the \"vtop\" command on Xen PAE kernels. o x86, x86_64: Support running against live pv_ops/Xen guest kernels. o x86, x86_64: Support xendump ELF dumpfiles generated from pvops/Xen guest kernels. o Determine the bit positions of PG_reserved and PG_slab using the newer pageflags enumerator values if available. o Prevent the \"repeat\" command from keeping a crash session alive if the controlling terminal session is killed.
* Wed Jul 14 2010 ptesarikAATTnovell.com- crash-compressed-booted-kernel: correctly find the booted kernel even if compressed (bnc#581159).
* Tue Jun 22 2010 ptesarikAATTnovell.com- Update to 5.0.5 o Add \"bt -F\" flag: same as \"bt -f\" but symbolic expressions are preferred (similar to \"rd -S\"). o Fix for the %install stanza in the crash.spec file to check for the existence of the sial.so extension module. o Fix a confusing \"foreach:\" prefix in the error message displayed by the \"crash -x\" command line option when the pre-loading of an extension module fails. o x86_64: Fix \"bt\" and \"bt -E\" if the kdump-generated NMI interrupts a task that has just entered kernel space but has not yet changed the RSP register to the kernel stack. o x86: Fix \"bt\" if the crash occurs during the execution of a kernel module\'s init_module() function. o Fix \"kmem -[sS]\" on 2.6.34 and later CONFIG_SLUB kernels, which changed the kmem_cache.cpu_slab[NR_CPUS] array to be a per-cpu offset value. o Show hexadecimal values in the \"INDEX\" colum of \"kmem -p\", because because \"page.index\" is typically a shared-use field that may also contain a pointer value. o Fix \"kmem
\" if the kernel\'s free page lists are corrupt, or in a state of flux, and cannot be followed. o Support newer \"virsh dump\"-generated KVM formats that may contain \"block\" and \"kvmclock\" devices in the dumpfile header. o Support \"virsh dump\"-generated KVM dumpfiles of a RHEL5 guest from a RHEL6 host, and to support dumpfile format changes that contain \"apic\" and \"__rhel5\" devices. o Fix a compiler warning when building gdb_interface.c with -O2. o Fix compiler warnings when building net.c with -O2.
* Mon Jun 21 2010 ptesarikAATTnovell.com- Update to 5.0.4 o x86: Fix \"bt\" when a newly-forked task\'s resumption EIP value points to \"ret_from_fork\". o x86: Fix \"bt\" when an NMI interrupts a task early during system call entry. o x86_64: Fix \"bt\" on 2.6.29 and later to recognize and display exception frames generated by exceptions that do not result in a stack switch, such as general protection faults. o ppc64: Account for an update to the kernel patch for CONFIG_SPARSEMEM_VMEMMAP. o Improve \"dev -p\" error message on 2.6.26 or later kernels, which no longer have the \"pci_devices\" global variable. o s390(x): Display \"CPU offline\" when doing a backtrace of the \"swapper\" task on an offline CPU. o x86_64: Fix per-cpu symbols on 2.6.34 and later kernels by allowing them to be of type \'d\' or \'D\'. o x86_64: Fix a segmentation violation during initialization in x86_64_get_active_set(). o Support KVM dumpfiles created with \"virsh dump\" that create \"cpu\" header sections using a QEMU CPU_SAVE_VERSION version greater than the supported version of 9. o x86_64: Fix for KVM dumpfiles created with \"virsh dump\", whose kernels have a \"_text\" virtual address higher than __START_KERNEL_map. o Add a \"map\" command for specifying the memory map of KVM guest dumpfiles created with \"virsh dump\". o x86_64: Correctly calculate the physical base address of a fully-virtualized RHEL6 guest kernel running on a RHEL5 Xen host. o x86_64: Fix \"bt\" on inactive (blocked) tasks for 2.6.33 and later kernels, which have the \"thread_return\" symbol removed from the embedded \"switch_to\" macro. o x86: Fix for \"bt\" on 2.6.33 and later kernels, which moved the \"system_call\" symbol to the .kprobes.text section. o Fix a segmentation violation in the \"trace\" extension module, as seen when running \"trace show -c \". o Add a \"trace dump -t\" command for the \"trace\" extension module.
* Tue Apr 20 2010 bernhardAATTbwalle.de- Update to 5.0.3 o Fix for running against 2.6.34 and later kernels to recognize and handle changes in the kernel\'s per-cpu data symbol naming, which no longer prefixes \"per_cpu__\" to declared per-cpu symbol names. o Fix for \"swap\" and \"kmem -i\" commands on 2.6.29 or later, big-endian, ppc64 kernels, where the swap_info_struct.flags member was changed from an int to a long. o Fix for the \"vm\" and \"ps\" command\'s task RSS value on 2.6.34 or later kernels. o Fixed \"possible aternatives\" spelling typo used in informational messages when an incorrect/unknown symbol name is used in \"rd\", \"dis\", \"sym\" and \"struct\" commands. o Fix for CONFIG_SPARSEMEM kernels that are not configured with CONFIG_SPARSEMEM_EXTREME. o Change the output of the \"kmem -[cC]\" options to indicate that they are not supported when that is relevant.- Refresh crash-compressed-kernel and crash-sles9-time.patch.
* Thu Apr 01 2010 ptesarikAATTnovell.com- crash-missing-declarations.patch: add a missing include (fixes compilation on ppc64).
* Mon Mar 29 2010 ptesarikAATTnovell.com- Update to 5.0.2 o Fix \"mod -[sS]\" if the attempt to load a kernel module fails due to an internal gdb error. o Avoid recalculation and modification of module symbol values from their CONFIG_KALLSYMS-generated values. o Fix a bug in reading some dumpfiles created with the \"snap\" extension. o s390, s390x: fix several bugs in the stack backtrace code. o x86, x86_64: fix \"mach -m\" if the BIOS-provided e820 map contains unusable EFI-related memory type values. o Fix the \"bool\" type in SIAL. o x86: avoid a stream of harmless but annoying error messages when running \"crash -d4\" (or any larger -d debug value). o Fix \"kmem -s list\" on non-CONFIG_SLUB kernels that contain a \"cache_chain\" symbol instead of a \"cache_chain\" macro. o x86_64: let \"bt\" use the stored frame pointers if the kernel was compiled with CONFIG_FRAME_POINTER. o ppc64: show the number of online cpus in the initial system banner and the \"sys\" and \"mach\" commands. o x86_64: fix the stack frame size calculator on kernels that were built without CONFIG_FRAME_POINTER. o Avoid an endless loop on EOF from /dev/tty. o \"ps -t\": display utime and stime values unmodified on kernels that store them in a cputime_t. o x86: fix \"bt\" if the kdump-generated NMI interrupts a process in kernel space before the full user-mode exception frame gets written on the kernel stack. o x86: fix \"bt -e\" on 2.6.30 or later if crash is compiled with - D_FORTIFY_SOURCE. o Fix initialization-time failures on 2.6.34 and later kernels built with CONFIG_NO_BOOTMEM. o ppc, ppc64: fix the displayed processor speed. o ppc64: support for an IBM-proposed kernel patch for CONFIG_SPARSEMEM_VMEMMAP kernels that will store vmemmap page mapping information. o Fix \"kmem -[sS]\" on live CONFIG_SLAB systems to prevent the redundant reading of the shared array_cache object list from the per-node kmem_list3 data structures.
* Sat Mar 20 2010 bernhardAATTbwalle.de- Update README.SUSE: o The search paths are no longer SUSE specific. o The command \'extend sial.so\' (with suffix) is needed to load the SIAL extension.
* Fri Mar 12 2010 bernhardAATTbwalle.de- Fix sps command from SIAL ps.c for kernel >= 2.6.29.
* Tue Feb 23 2010 ptesarikAATTnovell.com- crash-rl_digit_loop-return.patch: add the missing return to the embedded readline.
* Tue Feb 23 2010 ptesarikAATTnovell.com- Update to 5.0.1 o Fix \"irq\" on 2.6.33 and later kernels. o Fix \"swap\", \"kmem -i\", and \"vm -p\" on 2.6.33 and later. o Fix \"bt\" on an ia64 \"INIT\" process that interrupted a task that was running in user space, but was unable to modify the original (interrupted) task\'s stack. o Fix \"bt\" on offline s390/s390x \"swapper\" idle tasks. o x86, s390, s390x, ia64: use the highest online CPU number plus one as the system CPU count. o Correctly recognize per-cpu variables. o Let \"struct\" or \"union\" fail gracefully if given an unmapped or non-existent address. o Fix support of >4GB Xen domU dumpfiles. o Account for the renaming of the st_status_fixed_logout _lowcore struct member in 2.6.33 and later s390 and s390x kernels. o Add a defensive mechanism to handle corrupted \"cache_cache\". o Fix a startup segfault with 2.6.30 or later x86_64 dumpfiles from kernels compiled without CONFIG_SMP. o Fix a startup segfault if a kernel crashes while loding a kernel module. o Fix build failures with gcc-4.5 on x86_64. o Use mkstemps() from the built-in libiberty.a to allow running crash with pre-2.11 glibc versions. o Accept gdb-7.0 disassembler output on 2.6.20 and earlier x86 kernels. o Fix a gdb-7.0 regression that prevented \"dis -l\" from showing line numbers for some x86 base kernel text addresses. o Preparation for future s390x ELF dumpfile format.- Delete crash-large-xendump.patch: now solved in mainline.
* Fri Feb 12 2010 ptesarikAATTnovell.com- crash-large-xendump.patch: properly handle xendumps larger than 4GBs. (bnc#542170)
* Fri Feb 12 2010 ptesarikAATTnovell.com- crash-Makefile-ADD_CFLAGS: remove Upstream has honoured the CFLAGS settings since 4.0-8.12.
* Fri Feb 12 2010 ptesarikAATTnovell.com- Update to 5.0.0 o Update embedded gdb to FSF gdb-7.0. o Always recognize and display BUG()-induced exception frames when doing a backtrace on 2.6.29 and later x86_64 kernels. o Fix \"ps -r\" segfaults with 2.6.25 or later. o Fix \"mount\" on 2.6.32 and later (except \"mount -i\", which cannot be easily implemented for these kernel versions). o Recognize VMEMMAP_REGION virtual addresses in 2.6.26 and later ppc64 kernels compiled with CONFIG_SPARSEMEM_VMEMMAP. o Fix a 4.0-8.11 regression in determining the number of cpus on ppc64. o Fix \"irq\" on ppc64 kernel which do not define \"irq_desc_t\" as a typedef for \"struct irq_desc\". o Avoid the unnecessary \"WARNING: sparsemem: invalid section number:\" message when doing \"rd\" or \"kmem\" on CONFIG_SPARSEMEM_EXTREME kernels.
* Fri Feb 05 2010 jengelhAATTmedozas.de- Construct an ExclusiveArch tag for specfile to match source-code capabilities
* Tue Jan 05 2010 ptesarikAATTsuse.cz- Update to 4.1.2 o Fix initialization failure with 2.6.31 or later x86_64 CONFIG_NEED_MULTIPLE_NODES kernels running on systems that have multiple NUMA nodes. o Fix the snap.c extension module to properly handle NUMA systems with multiple nodes, or single-node systems whose first unity-mapped PT_LOAD segment starts on a non-zero physical address. o Fix \"bt [-t|-T]\" on x86 when the backtrace passes through three stacks (hard IRQ, soft IRQ, process). o Do not warn about \"non-process stack address for this task\" when \"bt -S\" is given a legitimate hard or soft IRQ stack address, or an x86_64 exception stack address. o Add a defensive mechanism to handle corrupt ELF core headers. o More non-functional changes for future integration of gdb-7.0 and for addressing Fedora packaging guidelines.- fixed reference to an uninitialized struct member
* Mon Dec 07 2009 ptesarikAATTsuse.cz- Update to 4.1.1 o Add \"lsmod\" as a built-in alias for the \"mod\" command. o Enhance \"bt\" on x86_64 to display which one of the five exception stacks it is operating on. o Add defensive mechanism to handle corrupt Elf32_Nhdr/Elf64_Nhdr structures in an ELF vmcore. o Fix DEBUG exception stack size and stack base address on 2.6.18 and later x86_64 kernels. o Fix session initialization failure with 2.6.30 and later x86_64 kernels if the number of possible cpus equals the kernel\'s configured NR_CPUS. o Fix potential session initialization failure with 2.6.30 and later x86_64 kernel dumpfiles filtered by makedumpfile. o Fix \"mach -c\" on 2.6.30 and later x86_64 kernels. o Preparations in the top-level source code for the integration of gbd-7.0. The current embedded version remains gdb-6.1.
* Fri Oct 09 2009 ptesarikAATTsuse.cz- Update to 4.1.0 o Fix \"extend\" regression on s390x and x86, introduced in crash 4.0.9 with the \"-x\" option o Cleanup top-level source files to address compiler warnings generated by the CFLAGS used in the Fedora build environment o Fix \"pte\" on s390 and s390x if the pte value argument evaluates as not present o Allow command redirection to pipes or files when using gdb commands alone on the command line without preceding it with \"gdb\" o Fix the processing of bit fields on big endian systems in the SIAL extension module o Fix \"dis -l\" to properly display line-number information for 2.6.21 and later x86_64 kernel module text addresses o Prevent querying the embedded gdb module for line numbers of kernel module text addresses if the module\'s debuginfo data has not been loaded o New option \"ps -G\" to restrict the process status output to the thread group leader of a thread group o Several fixes for the \"repeat\" command when used in conjunction with an input file. Without the patch: - Depending upon the command executed from the input file, a SIGINT would kill the command currently being executed from the input file, but the \"repeat\" command would then restart it. - If a command in the input file redirected its output to a pipe, the repeat operation could stop prematurely after executing that particular command. - If a command in the input file redirected its output to a pipe, the zombies of the command being piped to would not be cleaned up until the repeat command was stopped. - If the last command in the input file redirected its output to a pipe, all subsequent executions of the input file would only display the output of that last command. o New extension: \"trace.so\" o Fix for a potential failure to initialize the kmem slab cache subsystem on 2.6.22 and later CONFIG_SLAB kernels if the dumpfile has pages excluded by the makedumpfile facility o Fix a potential session initialization failure on x86_64 kernels if the dumpfile has pages excluded by the makedumpfile facility o Fix \"kmem -z\" on 2.6.29 and later kernels o Fix \"irq\" on 2.6.29 and later CONFIG_SPARSE_IRQ kernels o Fix \"kmem -i\" on 2.6.31 kernels o Fix \"kmem -i\" on x86_64 running 2.6.26 through 2.6.30 o Fix \"kmem -p\" on older 64-bit kernels that have a 32-bit page.flags field o Fix \"kmem -i\" on older kernels whose unreferenced page.count value was -1 (instead of 0) o Change the cursor location when cycling through the command history in \"vi\" editing mode (the default)
* Fri Oct 09 2009 ptesarikAATTsuse.cz- Update to 4.0.9 o New mainline versioning o Wholesale replacement of the x86/x86_64 disassembly code in the embedded gdb-6.1 module to that used in gdb-6.8 to correctly decode the 5-byte NOP used by the function tracer o Fix compressed diskdump/kdump vmcores to properly handle page descriptor structures that are located beyond a 4GB file offset in the vmcore file o Fix the \"sym
\" command option when the address references a symbol in the vsyscall FIXMAP virtual address page in certain x86_64 kernel versions o Multiple fixes for the \"bt\" command on x86_64: - properly recognize vsyscall FIXMAP virtual addresses when encountered as the RIP in an exception frame. - always use the NMI exception stack when available, not the per-cpu IRQ stack of an active non-crashing task - correctly determine the frame just above an IRQ interrupt exception frame, or above an exception frame that gets handled on the process stack, such as a page fault - correctly calculate the frame size to differentiate between text return addresses and the precise text RIP address of an exception o Fix usage of a System.map file argument with 2.6.30 and later kernels to avoid \"crash: symbol count overflow (trace_kmalloc)\" messages o Fix usage of a System.map file argument whose symbol list does not contain an \"_end\" symbol. o Fix \"kmem -p
\" or \"kmem
\" when
is not a page structure address to avoid the annoying \"kmem: WARNING: sparsemem: invalid section number: 8192\" messages o Fix the snap.so extension module when run on pre-2.6.31 x86_64 kernels with more than 4GB of physical memory o Fix build of the snap.so extension module on older systems running with \"make\" versions 3.80 or earlier o Fix build of the sial.so extension module if /usr/bin/bison and /usr/bin/flex do not exist on the host build system o Fix for the \"rd\" and \"vtop\" commands on RHEL4 x86_64 Xen paravirtual kernels in the reading or translation of vmalloc addresses that are not in kernel module vmalloc address space o New command line option \"-x\" to automatically load extension modules
* Fri Oct 09 2009 ptesarikAATTsuse.cz- Update to 4.0-8.12 o Support for the KVM \"save-vm\" file format o Support for 2.6.30 and later x86 CONFIG_4KSTACKS kernels, where hardirq_ctx[] and softirq_ctx[] arrays were changed to per-cpu o Replace the CFLAGS definition in the Makefile with a CRASH_CFLAGS definition, which in turn contains ${CFLAGS} to allow user-defined CFLAGS on the \"make\" command line o Bail out with a \"not a supported file format\" error immediately when trying to open x86 vmlinux file on an x86_64 host o Fix the \"bt\" command on x86 Xen hypervisor dumpfiles where a vcpu received a shutdown NMI while running in an interrupt handler o Correct cpu accounting when processors have been taken offline using a new get_highest_cpu_online() utility function o Fix a segmentation violation when running against kernels built with Fedora gcc version 4.4.0-12 and later, which introduced a more compact Dwarf 3 DW_AT_data_member location o Clean up gdb header files that generate warning messages when compiling the top-level cmdline.c file with \"make warn\" or \"make Warn\"- Delete crash-4096-cpus-x86_64.diff: Mainline.
* Thu Jul 02 2009 ptesarikAATTsuse.cz- Update to 4.0-8.11 o Fix the mapping of CPU to NT_PRSTATUS notes in kdump ELF dumpfiles; if a CPU was offlined, this mapping is not identity o Enhance the \"dev\" command to show CDEV and GENDISK o Fix the OPERATIONS column of \"dev\" o Fix potential SEGV when running \"foreach bt\" on a live system with many processes starting and ending o Fix reading of LKCD Version 8 and later x86 dumpfile headers o Fix backtraces of non-crashing CPUs interupted during process switch (x86_64) o Fix backtrace when transitioning from the IRQ stack to the process stack on 2.6.29 and later (x86_64) o Enhance \"runq\" to show the current task in each CPU\'s runqueue o Fix a memory leak when running on live systems o Allow using vmlinux files with DWARF3 debuginfo o Allow any order of arguments with a System.map file o Add several new defensive mechanisms to prevent potential errors and SEGVs when using non-matching vmcore, System.map and vmcore files o Adjust several virtual and physical memory address definitions for 2.6.31 x86_64 kernels o Improve \"kmem -s\" or \"kmem -S\" options with CONFIG_SLUB when an invalid slab page link address is encountered
* Thu Jul 02 2009 ptesarikAATTsuse.cz- Update to 4.0-8.10 o Enhance directory search for \"mod -S \" so that it is now possible to use an alternate module/module-debuginfo directory tree, created with rpm2cpio in a non-root directory o NEW: \"--mod\" command-line option to override the default location of the module directory tree o NEW: snap.so extension to create a kdump or netdump dumpfile from a live system (x86, x86_64, ppc64, ia64 only) o Recognize cpu_
*_mask symbols on 2.6.29 o Handle the removal of x8664_pda from 2.6.30 o Use \"crashing_cpu\" to determine a kdump x86_64 panic task o Add \"./extensions\" to the list of directories searched for the \"extend\" command. The order is now: 1. the current working directory 2. the directory specified in the CRASH_EXTENSIONS shell environment variable 3. /usr/lib64/crash/extensions (64-bit architectures) 4. /usr/lib/crash/extensions 5. ./extensions o Rebuild extensions when defs.h is modified o Add several function prototypes for the SIAL extension module to fix incompatible int size on 64-bit o Enhance the extension modules API with a set of functions to get the register set from an NT_PRSTATUS note if available o Fix a SEGV when the panic task cannot be determined from a ppc64 kdump vmcore
* Mon Apr 27 2009 ptesarikAATTsuse.cz- Update to 4.0-8.9 o NEW: Add option \"bt -g\" to display the backtraces of all threads in a thread group o NEW: Support for kdump \"split-dumpfile\" format produced by \"makedumpfile --split\" o Fix for \"kmem -i\", \"kmem -n\" and \"kmem -p\" on x86_64 CONFIG_SPARSEMEM and CONFIG_SPARSEMEM_EXTREME kernels that have MAX_PHYSMEM_BITS increased from 40 to 44 o Allow multiple \"--machdep option=value\" command-line options o Produce a warning if \"bt\" is attempted on active, non-crashing, xen dom0 tasks using kdump dumpfiles o Fix for potentially empty \"bt -t\" output, and for \"bt -T\" potentially dumping the text return addresses in the hard or soft IRQ stacks instead of the process stack
* Tue Apr 21 2009 ptesarikAATTsuse.cz- Update to 4.0-8.8 o Add the CONFIG_STRICT_DEVMEM hint when reading /dev/mem fails o Fix segmentation violation in \"bt\" when reading certain x86_64 Egenera/LKCD dumpfiles where the starting stack hooks o Fix the \"log\" command for cases when the log buffer was cleared with syslog() or klogctl() o Improve the error message displayed by \"bt -S\" when given a non-process stack address as an argument o Search directories for the \"extend\" command in this order: 1. the current working directory 2. the directory specified in the CRASH_EXTENSIONS shell environment variable 3. /usr/lib64/crash/extensions (64-bit architectures) 4. /usr/lib/crash/extensions o Improve how the \"bt\" command determines which PID 0 swapper task was interrupted by an ia64 INIT or MCA exception o Remove an unused initialized variable in get_task_mem_usage() o Add a debug-level 8 statement in readmem() to display the current input address and its translated physical address under the existing debug-level 4 \"\" line- Delete crash-improve-find-extension.diff: Solved slightly differently in mainline.
  
ICM