Subject: Re: forwarded message from Chet Ramey (Re: bash-1.14.5 crashes)
To: David Gilbert <dgilbert@pci.on.ca>
From: J.T. Conklin <jconklin@netcom.com>
List: current-users
Date: 09/13/1995 23:31:43
> > Configuration Information [Automatically generated, do not change]:
> > Machine: sun4
> > OS: NetBSD
> > Compiler: gcc
> > 
> > Description:
> > 	A core dump with the following backtrace is produced by internal-cd
> > 
> > Program terminated with signal 10, Bus error.
> > #0  0x5d168 in _catclose ()
> > (gdb) bt
> > #0  0x5d168 in _catclose ()
> > #1  0x5cc00 in _catopen ()
> > #2  0x5c640 in __strerror ()
> > #3  0x58d50 in strerror ()
> 
> This looks like a problem with the NetBSD C library.
> 
> You might look at the core file and see what `errno' is set to.  Maybe
> it's out of bounds and strerror is stomping on memory somewhere.


I don't think we can trust this stacktrace.  _catopen() doesn't call
_catclose().  I beleive that strerror handles error conditions (errno 
out of range / bad message catalog / missing message catalog / etc) 
correctly.  Perhaps things are screwed up already?  ie. why would a
cd be calling strerror in the first place?

	--jtc