> >
> > This doesn't help a lot. How about building bash-4.2.42 with -g so
> > debugging symbols are preserved, then seeing where the crash is?
> >
>
> I compiled 4.2.42 using gcc 4.6.3 (C[XX]FLAGS="-march=native -O2 -g"). It
> took longer before the crash occurred and this is the report I got:
>
> malloc: ./read.def:696: assertion botched
> free: called with already freed block argument
> Aborting...catch.
OK. What version of Linux are you using? Maybe I have that and will be
able to reproduce it more easily.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
