Re: redisplay crash: here we go agaaaaaaaaaaaiiiiiiiiiiiiiiiiiiiiiiiin!!!!!

Andy Piper wrote: no it didn't. there was careful caching to avoid this, and the places that called lisp code were explicitly placed outside of the critical section boundaries. the change you made was to write more code that was comparable to the stuff outside of the critical section boundaries, i.e. calling lisp and such, but place it within the critical section. in any case, i think i may have discovered the cause of this crash. it relates to bad coding inside of the functions that build up the display lines, so that you end up with two different display lines pointing to the same object, which then gets freed twice. unless someone worked on this recently, this has been a latent bug present for a very long time. and ... it's a perfect candidate for being caught by a sledgehammer checker. andy, is there any possibility you could find some time to write such a checker? i'd consider doing it, but you know more about the guts of redisplay and i'm busy with the mule work and such. please? pretty please? i'd totally appreciate it and so would xemacs :-}