Codelite 5 Problems running release versions

[wittend]

Eran,

Thanks. I installed and ran the debugger on both release and debug builds. They run properly with no segfaults to debug. But when I try to run the same executables without the debugger, they segfault as before. This should tell me something, but I'm not sure what that is. In any case, there is no crash, so no call stack to copy.

I guess GDB is redirecting calls to a more suitable environment. Not sure what to look at next.

Dave

[wittend]

Hmmm, then I thought I should just reboot everything on general principle. When everything came back up, the debugger doesn't work anymore. Python 2.73 is definitely in the system path.

Windows (or something) keeps replacing the copy of codelite.xml in "C:\Users\wittend\AppData\Roaming\CodeLite\config" with a version that references Mingw-4.6.1 (a location which no longer exists).

Very strange.

Dave

[wittend]

Well, for want of anything better to try, I did an extra thorough 'rip it out by the roots' de-install of anything connected with Codelite. Then I did a careful reinstall of *everything* - as administrator - and so far it seems to be working. Third time is a charm! The only thing that does not seem to work is the gdb2012-08-17, which I can live without for now.

Who knows how I had offended the compiler gods this time. I think that I'll go sacrifice a chicken.

Thanks!

Dave

[eranif]

Hmmm, then I thought I should just reboot everything on general principle. When everything came back up, the debugger doesn't work anymore. Python 2.73 is definitely in the system path.

Windows (or something) keeps replacing the copy of codelite.xml in "C:\Users\wittend\AppData\Roaming\CodeLite\config" with a version that references Mingw-4.6.1 (a location which no longer exists).

Very strange.

Dave

Make sure that you close codelite when u modify codelite.xml file (otherwise codelite will override it on exit)
(Never liked windows other than playing machine )

Eran