Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Eduardo Bustamante Newsgroups: gnu.bash.bug Subject: Re: [PATCH] A terminating signal has to complete a bash process Date: Mon, 21 May 2018 08:55:38 -0500 Lines: 36 Approved: bug-bash@gnu.org Message-ID: References: <20180430220520.32312-1-avagin@openvz.org> <20180501164422.GA7043@outlook.office365.com> <759a8efe-1c0a-2966-a2ae-59fc734fdad3@case.edu> <20180501235553.GA4218@outlook.office365.com> <6eb002a4-5cbc-1955-e3bd-f1eed5c2fd20@case.edu> <20180521054213.GA12008@outlook.office365.com> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: usenet.stanford.edu 1526910965 16298 208.118.235.17 (21 May 2018 13:56:05 GMT) X-Complaints-To: action@cs.stanford.edu Cc: Chet Ramey , Andrei Vagin , bug-bash To: Andrei Vagin Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BJ5rlnr5MYxZYTNh0qTLNcTobFKoeV9eyL/i4LNQfok=; b=uKMz+Aq04ZpaFrlod7F8ynSgQSN8bNjqfvXsgdNTvpfXH3XnHYMFr+y0S0kCdDOPcV gW9yXnyobiq3jZ7ypLW7mpHTmpquun4zKfXAmyvhcWFYkX/OFUf3QuEb7+Lc/LhyM30Y qKPL1VMtWaHbm0hSKG1AXu5Ab4Zu7tDa73GEs6q4G+GIxudW900sIr8/FFCB2pn/1I4R EW/xyyFuIIrOdGInz1kGKucheYiguswJDngsK//8hvrhAKQckJDmL4Tk5D3JpDzez2b3 VMiBnr3PuYhriS3kn+GtSfvel8QWMMNkmv//O39eaCoUrLkFRD5h6TD3PtjCXxjnplfM 6O9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BJ5rlnr5MYxZYTNh0qTLNcTobFKoeV9eyL/i4LNQfok=; b=Cgwx9Afu0yLwDoXE7cQpss2gsEmqhYgUNfTph+H+zZ/xyK39pMBP5w0723+vzhDwtA K3O4DeKEm5XPDyj4MoW1lX/qrZW/ounzc1ofMFtY815Js/2Kjo9v7BsORERxyUC880Aw tedTMUts++J++b32WRDwFzh1lS6E6yqTk/BvVngBn55PSpO/lKcjqDZv+9bWy11B1e80 Ev8KurpZT1BeupgKZ+oEqnXUyJm/soAUuPvDC5brqFZlmhmoM+ly6NDqoF4M8Drt/Ds6 7PTCA7MDBY1lJb9O8RezTuRUBhPAp/hiakzGOeI1qu1q5cBGvn5T6VWoS9TxUu5CI3wQ O46w== X-Gm-Message-State: ALKqPwde9myqILXb9H1kwK/EdLH/yHYIYH/Fy7rBi89FSY/WVGeXj1Ox 5ZUIYdX4k95S84nadXg/I4Cqt5p1DSlVPrV08dI= X-Google-Smtp-Source: AB8JxZqV5konEHk4TNqrAqiKMFCoaE/XKJmB0ci5tFKWMG70cHRYAk4t+PkEF07gA6Oq+LbPlC42/l+GxTF35+b9sGk= X-Received: by 2002:a2e:3e0c:: with SMTP id l12-v6mr12926442lja.23.1526910959557; Mon, 21 May 2018 06:55:59 -0700 (PDT) In-Reply-To: <20180521054213.GA12008@outlook.office365.com> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4010:c07::242 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14120 It's in commit 96b7e26874047647e85bd5c7e71a7f664174c2cc, in the `devel' branch of the git repository. On Mon, May 21, 2018 at 12:42 AM, Andrei Vagin wrote: > Hello Chet, > > Have you had a chance to try this patch? Let me know if you will have > any questions. > > Thanks, > Andrei > > On Thu, May 03, 2018 at 04:29:13PM -0400, Chet Ramey wrote: >> 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/ >