On Tue, 19 Jul 2011, Russell Harmon wrote: Greetings, Russell,
For some time now, I've been getting random crashes from different applications. Mostly, gvim, but zsh sometimes crashes too. In fact, I've got a zsh script that if I add a blank line in a particular place, it triggers a crash.
Have you tried using bash for your initial shell instead of zsh? Under this scenario, does gvim still crash?
For zsh, it seems to happen fairly deterministically; if it's crashing, it keeps crashing. If I add an empty line in the right spot, it works and keeps working.
Hmm...that sounds suspiciously line-termination related.
For gvim, it seems to happen randomly; often times even if gvim starts successfully, it fails I assume after forking but before exec. I've pasted the error printed when it fails below. 0 [main] gvim 3008 exception::handle: Exception: STATUS_ACCESS_VIOLATION *** starting debugger for pid 3008, tid 6748 Coredumps for both zsh and gvim can be found at http://files.eatnumber1.com/zsh.exe.core http://files.eatnumber1.com/gvim.exe.core These coredumps however weren't helpful to me. I've pasted my interaction with gdb below so you can see why. $ gdb -q -core gvim.exe.core [New process 1] [New process 0] [New process 0] #0 0x777efb8a in ?? () (gdb) bt #0 0x777efb8a in ?? () (gdb) quit Any thoughts on how I can debug this problem?
Switch shells to bash and see if the gvim failure still occurs. If not, then it's likely zsh internals related. As with most problems, please collect the information as per: http://cygwin.com/problems.html But, before that, are you on a fairly recent version of all (or most) packages?
-- Russell Harmon
-- Peter A. Castro <doc...@fruitbat.org> or <peter.cas...@oracle.com> "Cats are just autistic Dogs" -- Dr. Tony Attwood
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple