c1f10d11bc
Since the ps command handles signals with it's own handler, it doesn't create core files when something wrong happens. The attached patch restores the ps command ability to create core files by calling the default handler once we print our custom message. The original RH's workaround masked SIGABRT and SIGSEGV signals and that would conflict with the original intention of the custom signal handler and also with the filtering patch I sent in my previous email. Moreover, this solution generates core for all relevant signals (SIGFPE, etc.). Bug-Redhat: http://bugzilla.redhat.com/871825 Bug-Redhat: http://bugzilla.redhat.com/512857 Reference: http://www.freelists.org/post/procps/PATCH-Allow-core-file-generation-by-ps-command-rhbz871825-rhbz512857 Signed-off-by: Craig Small <csmall@enc.com.au>
COMPATIBILITY
This code is intended for use with Linux 2.6.xx, 3.x and
hopefully all future kernels.
INSTALLATION
If you are using git version of the project you need extra step.
./autogen.sh
After that, and everyone using .tar.xz version of procps-ng, can
do normal build. Read './configure --help' to select options for
your needs.
./configure
make
make install
If you have DejaGNU installed you can run optional test suite.
make check
HOW TO CONTRIBUTE
See Documentation/BUGS file.
PACKAGING
If you are a downstream maintainer (packager) for a Linux
distribution, please avoid causing troubles. This section
applies to you.
Avoid maintaining distribution specific patches. Send your
patches to upstream, where they are at least reviewed, if not
included.
Please forward bug reports. If your bug database is public and
busy enough to bother with, please make this known. Follow
Debian's lead in making the bug database easy to comment on via
email without need for an account.
For normal packages, ensure that you do not add debugging flags
to the CFLAGS variable.
UPSTREAM & BUG REPORTS
procps-ng <procps@freelists.org>