Around about 19/04/06 12:07, Bram Moolenaar typed ...
Apparently your FileChangedRO autocommand does something nasty. I suspect we need to detect that nastyness and disallow it. Any idea what the nasty bit could be?
I tried making a cut down fake version, but that always worked. It's essentially doing a couple of system() [vim] calls, one's a 'cat' of a config file, the next is the actual remote sourcesafe checkout command (via rsh), of each of which it parses the output.
Then it does a :edit to reload the buffer and a 'syntax on'. ISTRT if I comment out the :syntax on' it stops crashing, but I then get a file with no syntax highlighting (even though it was on before). Maybe that in itself is the issue.
After some pointers go wrong anything can happen, thus how it crashes exactly is not interesting. It could help to use a library that forbids access to freed memory, like efence. Then the error is detected much earlier and a stack trace may provide more useful info.
ef is not reporting anything [except its banner], although it does make it not crash fatally [locked after crash], albeit with the corrupted text as a spell replacement. Any other recommended tools?
-- [EMAIL PROTECTED] ~]# rm -f .signature [EMAIL PROTECTED] ~]# ls -l .signature ls: .signature: No such file or directory [EMAIL PROTECTED] ~]# exit
