On 1/24/13 11:32 AM, konsolebox wrote: > Hi. Thanks for the attention. Here's a backtrace:
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?
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/
