It is ksh itself that is dumping core.  This is NetBSD 1.6

Here is the backtrace:
#0  0x8048c6d in ablockfree (bp=0x72617764, ap=0x80c2020) at alloc.c:469
#1  0x8048b28 in afree (ptr=0x80dd268, ap=0x80c2020) at alloc.c:417
#2  0x806ff36 in setstr (vq=0x80d6ae0, 
    s=0x80dd03d "<option type=\"hardware\" device=\"scsibus*\" parent=\"adv?\" enabled=\"1\"></option>\\n<option type=\"hardware\" device=\"scsibus*\" parent=\"adw?\" enabled=\"1\"></option>\\n<option type=\"hardware\" device=\"scsibus*\" "..., error_ok=1) at var.c:378
#3  0x8070b63 in typeset (
    var=0x80dd038 "temp=<option type=\"hardware\" device=\"scsibus*\" parent=\"adv?\" enabled=\"1\"></option>\\n<option type=\"hardware\" device=\"scsibus*\" parent=\"adw?\" enabled=\"1\"></option>\\n<option type=\"hardware\" device=\"scsib"..., set=0, clr=0, field=0, base=0) at var.c:732
#4  0x8058b75 in comexec (t=0x80caaa8, tp=0x0, ap=0x80cab18, flags=0)
    at exec.c:582
#5  0x8057d05 in execute (t=0x80caaa8, flags=0) at exec.c:158
#6  0x80584fa in execute (t=0x80ca958, flags=0) at exec.c:382
#7  0x8057ef3 in execute (t=0x80ca958, flags=0) at exec.c:199
#8  0x8058636 in execute (t=0x80c69b0, flags=0) at exec.c:402
#9  0x8058ecd in comexec (t=0x80cb5d0, tp=0x80c6960, ap=0x80de030, flags=0)
    at exec.c:674
#10 0x8057d05 in execute (t=0x80cb5d0, flags=0) at exec.c:158
#11 0x8057ece in execute (t=0x80cb5a0, flags=0) at exec.c:196
#12 0x8058636 in execute (t=0x80cb570, flags=0) at exec.c:402
#13 0x8058ecd in comexec (t=0x80d7180, tp=0x80cb530, ap=0x80da82c, flags=0)
    at exec.c:674
#14 0x8057d05 in execute (t=0x80d7180, flags=0) at exec.c:158
#15 0x80584fa in execute (t=0x80d4b48, flags=0) at exec.c:382
#16 0x8057ece in execute (t=0x80d7068, flags=0) at exec.c:196
#17 0x80584fa in execute (t=0x80d59c0, flags=0) at exec.c:382
#18 0x8058606 in execute (t=0x80d5918, flags=0) at exec.c:397
#19 0x8057ece in execute (t=0x80d79f0, flags=0) at exec.c:196
#20 0x805849a in execute (t=0x80c9100, flags=0) at exec.c:374
#21 0x8064f02 in shell (s=0x80c59a8, toplevel=1) at main.c:623
#22 0x80649ed in main (argc=2, argv=0xbfbfd808) at main.c:435
#23 0x804825c in ___start ()

Ben

On Sun, Oct 06, 2002 at 05:55:57PM -0700, Chuck Yerkes wrote:
> Is it ksh itself that's dumping core or some program called
> by the script is dumping core?
> 
> If so, look at that program more closely and talk to us.
> 
> Quoting collver1@attbi.com (collver1@attbi.com):
> > Hi,
> > 
> > I have a shell script that dumps core whenever I run it.  It is a CPU
> > intensive script.  But while watching "top", I never see the script use
> > more than 750k of RAM, so I doubt it is running out of memory.
> > 
> > The error is "Memory fault (core dumped)"
> > 
> > Could someone give me advice on tracking this down?  I'm going to try
> > running it with -x, and then try using ktruss.