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

Groups > gnu.bash.bug > #14089 > unrolled thread

Re: [PATCH] A terminating signal has to complete a bash process

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] A terminating signal has to complete a bash process Chet Ramey <chet.ramey@case.edu> - 2018-05-03 16:29 -0400

#14089 — Re: [PATCH] A terminating signal has to complete a bash process

On 5/1/18 7:55 PM, Andrei Vagin wrote:

>> If it's not obvious, I'm trying to determine whether making this change
>> will add any more value than simply exiting (perhaps with a particular
>> exit status).
> 
> It will add more value. Without this changes, we will not know whether a
> bach process crashed or exited. If it will not generate a core dump after
> a crash, the tools like abrtd, coredumpd, etc will not detect this crash
> and will not report about this abnormal behaviour.

OK, we'll try it. I'll be interested to see if any core dumps created by
causing a SIGSEGV will overwrite any stack information from the `real'
fatal signal.

Thanks for the patch.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web