Crashes due to borked xml config files
Posted: Thu Apr 10, 2014 12:54 am
Smallish thing to make codelite better.
When codelite starts up and one if it's config files is hosed, it'll just exit (this program has stopped working) Far as I can tell this is because xml based config files getting hosed (at least for me) when windows reboots after installing some patches at 3am while I'm running over night tests.
It's mostly an annoyance to me, but the other guy in my office basically just stopped using codelite after this happened so it's a barrier to entry.
PS: the corrupted xml files are always just truncated.
When codelite starts up and one if it's config files is hosed, it'll just exit (this program has stopped working) Far as I can tell this is because xml based config files getting hosed (at least for me) when windows reboots after installing some patches at 3am while I'm running over night tests.
It's mostly an annoyance to me, but the other guy in my office basically just stopped using codelite after this happened so it's a barrier to entry.
PS: the corrupted xml files are always just truncated.