[Crash-utility] [ANNOUNCE] crash version 7.2.3 is available

One of the more annoying maintenance chores is dealing with a new compiler version. In crash-7.2.2, there was this commit, which purported to fix several issues concerning new warnings generated from gcc-8.0.1 when building with -Wall or -Werror, all false alarms, but which rendered "make warn" or "make Warn" unusable: - Fixes to address several gcc-8.0.1 compiler warnings that are generated when building with "make warn". The warnings are all false alarm messages of type [-Wformat-overflow=], [-Wformat-truncation=] and [-Wstringop-truncation]; the affected files are extensions.c, task.c, kernel.c, memory.c, remote.c, symbols.c, filesys.c and xen_hyper.c. (anderson(a)redhat.com) In my annoyance and haste, three of the "fixes" introduced new bugs, which may or may not be encountered, depending upon what compiler version the crash utility was built with. Fortunately Alex Sidorenko caught one of the bugs, and upon code inspection, I found two more. Since the fixes caused fairly serious regressions, this immediate new release is the best course of action. I apologize for any inconvenience this may have caused. Download from: http://people.redhat.com/anderson or https://github.com/crash-utility/crash/releases The github master branch serves as a development branch that will contain all patches that are queued for the next release: $ git clone git://github.com/crash-utility/crash.git Changelog: - Fix for a crash-7.2.2 regression that may cause the "mount" command to generate a segmentation violation. The bug is dependant 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 varibles. (anderson(a)redhat.com) - 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. (anderson(a)redhat.com) - Fix for a third, highly unlikely, crash-7.2.2 buffer overrun regression, that could potentially occur during session initialization. (anderson(a)redhat.com)