I make a nigthly builds of codelite and two last versions is not accessible for testing for me. I always got a BSOD after a codelite run.
CodeLite Starting
Workspace loaded
No workspace tagging (it has already)
BSOD!
BSOD is only with releases I have made. I haven't got BSOD with last official release (r5589).
What could be a problem? Now I can't code in r5589. It often crashes when debugging or just when I work in editor with windows' standart stack crash error. My builds based on Eran's Inno Setup Scripts. Older builds worked properly. At this moment I have no complaints about my builds from users.
Windows 7 x86 Pro SP1
MinGW 4.7.0
BSOD Code: 0x000000F4 (smth about HDD errors, but HDD is OK)
Most of the changes since the last release have been in plugins (mostly CallGraph), which are unlikely to crash until they're run. The non-plugin change most likely to go wrong is in r5611 itself, and even that affected only 'Find' situations (and I tested it on MSWin without a problem).
I can think of 2 ways for you to investigate the problem:
Run CodeLite inside gdb. When it crashes see if the backtrace helps you. It'll obviously be better to test a debug build...
Try making a build of an earlier version and see if that crashes. I'd start with r5589, which is known to be good; if that crashes too it must be your build system that's causing it. If not, you can bisect: try r5600; if that's OK try r5605 etc. If it isn't, try r5595 (and so on).
Previous builds (before r5589) doesn't crash.Tried to get a memory crash dump and it is impossible now. After increasing pagefile.sys on system disk to 2GB r5611 runs without BSOD but sometimes it can reboot explorer and/or silently quit. Call Graph plugin is disabled. If I'll get a crash dump I'll post it here. Unfortunately, I haven't got experience in dump analysing and can't analyse it myself. I run it under OllyDebugger and make a screenshot. Maybe it can bring some useful information...
After passing an exception to program I got a message that program cannot process exception.
LastError in Registers Window is ERROR_FILE_NOT_FOUND (sorry for cut screenshot)
