🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.bash.bug
Article #386

Runaway bash

#386
From: James J Dempsey
Date: Wed, 26 Jul 1989 19:20
20 lines
1076 bytes
I use: Vax 8530, Ultrix 3.0, GCC 1.35, yacc, GNU make 1.35

I have had over a dozen cases where a bash of mine gets into some very
tight infinite loop and eats up gobs of cpu time.  I have tried to get
a core dump, but the only signal they will respond to is SIGKILL, so I
have been unsuccessful.

These runaway bashes must come from shells which are in the process of
exiting or X windows which are closing or something, because I never
notice when they get created.  Currently running interactive shells
don't go into this state.

This wouldn't bother me too much, except we are charged for cpu time
on this host.

Does anyone have any good ideas about how to debug this problem?

Thanks,

		--Jim--
Technical Details
Message-ID: <8907261931.AA29540@life.ai.mit.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!BBN.COM!jjd

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!BBN.COM!jjd
From: jjd@BBN.COM (James J Dempsey)
Newsgroups: gnu.bash.bug
Subject: Runaway bash
Message-ID: <8907261931.AA29540@life.ai.mit.edu>
Date: 26 Jul 89 19:20:30 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 20