You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 patches or crashes while codelite is running.
I suspect there are two issues. (maybe three)
if a file is missing then codelite just replaces it with the default. If a config file is corrupted, truncated, then codelite crashes hard when trying to read it. And it never get 'fixed'
I think a number of config files are updated on startup, but kept open and never flushed until codelite closes normally. So if windows drop kicks codelite the files are left partially written.
Possible when windows tried to tell codelite to quit it doesn't shut down orderly leaving windows to clean up open handles and such.
The text was updated successfully, but these errors were encountered:
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 patches or crashes while codelite is running.
I suspect there are two issues. (maybe three)
The text was updated successfully, but these errors were encountered: