Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: "Ayappan P2" Newsgroups: gnu.bash.bug Subject: RE: Issue with Bash Date: Fri, 31 Jul 2020 19:34:01 +0530 Lines: 80 Approved: bug-bash@gnu.org Message-ID: References: <76d97603-ac8b-1952-cb10-f178fd8989db@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: multipart/related; Boundary="0__=8FBB0F25DFDFA05F8f9e8a93df938690918c8FBB0F25DFDFA05F" X-Trace: usenet.stanford.edu 1596204256 8570 209.51.188.17 (31 Jul 2020 14:04:16 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org, "bug-bash", Rishita Saha16 To: chet.ramey@case.edu Envelope-to: bug-bash@gnu.org In-Reply-To: <76d97603-ac8b-1952-cb10-f178fd8989db@case.edu> X-KeepSent: 45ED3104:7A08B8C2-002585B6:004C26CF; type=4; name=$KeepSent X-Mailer: IBM Notes Release 10.0.1FP1 March 26, 2019 X-LLNOutbound: False X-Disclaimed: 33535 X-TNEFEvaluated: 1 x-cbid: 20073114-3165-0000-0000-00000411376E X-IBM-SpamModules-Scores: BY=0; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.394815; ST=0; TS=0; UL=0; ISC=; MB=0.000076 X-IBM-SpamModules-Versions: BY=3.00013569; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000295; SDB=6.01413749; UDB=6.00757872; IPR=6.01196029; MB=3.00033283; MTD=3.00000008; XFM=3.00000015; UTC=2020-07-31 14:04:06 X-IBM-AV-DETECTION: SAVI=unsuspicious REMOTE=unsuspicious XFE=unused X-IBM-AV-VERSION: SAVI=2020-07-31 10:26:50 - 6.00011666 x-cbparentid: 20073114-3166-0000-0000-00001AD33C31 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-31_04:2020-07-31, 2020-07-31 signatures=0 X-Proofpoint-Spam-Reason: orgsafe Received-SPF: pass client-ip=148.163.156.1; envelope-from=ayappap2@in.ibm.com; helo=mx0a-001b2d01.pphosted.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/31 10:04:10 X-ACL-Warn: Detected OS = Linux 3.x [generic] [fuzzy] X-Spam_score_int: -34 X-Spam_score: -3.5 X-Spam_bar: --- X-Spam_report: (-3.5 / 5.0 requ) BAYES_00=-1.9, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, TVD_FW_GRAPHIC_NAME_MID=0.095, URIBL_BLOCKED=0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: X-Mailman-Original-References: <76d97603-ac8b-1952-cb10-f178fd8989db@case.edu> Xref: csiph.com gnu.bash.bug:16661 --0__=8FBB0F25DFDFA05F8f9e8a93df938690918c8FBB0F25DFDFA05F Content-Transfer-Encoding: quoted-printable Content-type: text/plain; charset=ISO-8859-1 We are passing SIGHUP from another terminal ( not from the terminal which has the interactive bash shell) . The terminal which has the interactive bash closes immediately. The scenario is we just open two terminals. In one terminal , just invoke bash . And from another terminal pass SIGHUP to the parent process (ksh) of bash. Thanks Ayappan P From: Chet Ramey To: Rishita Saha16 Cc: bug-bash@gnu.org, chet.ramey@case.edu Date: 31-07-2020 19:05 Subject: [EXTERNAL] Re: Issue with Bash Sent by: "bug-bash" On 7/31/20 3:25 AM, Rishita Saha16 wrote: > Hi All, > > We have been able to recreate a scenario where bash dumps core immediately > on issuing a SIGHUP to the parent process (kill -1 ). On > debugging, the core so generated shows exactly the same stack trace as we > had seen with the previous core. Below is the truss output of bash process > when the parent process of bash (ksh, in this case) gets a SIGHUP: I'm trying to figure out the scenario here. An interactive bash, which is the child of an interactive ksh, runs `kill -1 $PPID'. The parent ksh apparently closes the controlling terminal (?), then resends the SIGHUP to its children (bash) before exiting. The interactive bash catches SIGHUP in readline, attempts to clean up the terminal by restoring the original settings, and gets SIGHUP (?), even though SIGHUP isn't one of the signals that's supposed to be sent when you use tcsetattr. I'd love to know what's happening to the controlling terminal here, assuming the scenario I've outlined is what's happening. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A=5F=5Ftiswww.cwru.edu= =5F-7Echet=5F&d=3DDwIDaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DSRx7SyASbvCxu7GP-= Qbph4o5MPmrwcLUo4BhenbwbOs&m=3DdREr3VV=5F1yXFT4jYksU27BGkTuQMzbiZ3YfMkA7Qiy= U&s=3DZK-DO14m3GM4ifbR8ncAmmgyyOuGzSAcm49s=5FTTrRQM&e=3D --0__=8FBB0F25DFDFA05F8f9e8a93df938690918c8FBB0F25DFDFA05F Content-type: image/gif; name="graycol.gif" Content-Disposition: inline; filename="graycol.gif" Content-ID: <1__=8FBB0F25DFDFA05F8f9e8a93df938690918c8FB@> Content-Transfer-Encoding: base64 R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7 --0__=8FBB0F25DFDFA05F8f9e8a93df938690918c8FBB0F25DFDFA05F--