Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1738945 > unrolled thread

Aborting a core dump on a fatal signal

Started byRaymond Jennings <shentino@gmail.com>
First post2017-09-25 13:20 +0200
Last post2017-09-25 13:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  Aborting a core dump on a fatal signal Raymond Jennings <shentino@gmail.com> - 2017-09-25 13:20 +0200

#1738945 — Aborting a core dump on a fatal signal

FromRaymond Jennings <shentino@gmail.com>
Date2017-09-25 13:20 +0200
SubjectAborting a core dump on a fatal signal
Message-ID<utzAC-5BH-11@gated-at.bofh.it>
Would there be any benefit to allowing an in-progress core dump to be
aborted if the dumping process receives a fatal signal?

Example:

Process segfaults, starts dumping core, but it has a lot of virtual
memory allocated so it promptly leads to a queue-clogging deluge of I/O
that takes in some cases several minutes to finish.

In between the time where it snags the crash signal and the time when
it finishes dumping and terminates, I'd like to be able to send it a
SIGKILL or something to abort the core dump.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web