🚀 go-pugleaf

In article <71ldkh$jgq$1@shell3.ba.best.com>,
	Smith and O'Halloran <inwap@best.com> wrote:
|
| In article <363a5c8b$0$29747@nntp1.ba.best.com>,
| 	  Kim DeVaughn <kimdv@best.com> wrote:
| >
| >In the past few days, I've had several of my shell scripts core dump for no
| >apparent reason.  These have been very different scripts, some of which have
| >been working for years without problems.  Subsequent execution of the same
| >scripts have been without incident.
|
| I have not seen that problem here, but some years back it bit me on a
| SunOS system.  The temporary workaround was to put
| 	DUMMY="1234567890"; export DUMMY
| in the script that called the one that failed.  It appeared that the failure
| occured only when the total size of the ENV variables was exactly n*1024.
| Then a new version of the OS came out and I never saw the problem again.

Hmmm.  Perhaps they were malloc'ing 1k chunks, and then didn't account for
adding a string terminating NULL, or some such.

FWIW, I thought that maybe having had my screen(1)s up for many days might
have had something to do with causing my mystery SEGV's (I dunno how, but
when you're grasping at straws ...).

Anyway, I killed 'em all off, and started fresh.  No unexplained crashes
since.  Coincidence?  Gnu only knows ...

/kim

============================================================================
"We create the government that screws you, and then you're supposed to thank
 us for protecting you from it."   --Congressman Vin Weber (R-Minn)