User forums > Help

Crash with last nighlty build

<< < (3/4) > >>

Elena:
Strange. I am 100% sure it crashed the other day and the folder with the .exe is still that of the nightly build which I installed 2 weeks ago or so but there is no .rpt.... When CB freezes that way, I can just ask Windows to close it forcibly (the hard way) so perhaps it is really unable to even just write out any crash report...

Miguel Gimenez:
The report is generated when crashing, a freeze will not generate it.

Elena:
Well I don't know how to properly call it... when it happens, I am always clicking in the code editor, move the mouse wheel and I realize that CB is not responding. So I know what I am before. It remains frozen and unresponsive for several seconds, even perhaps 30 seconds, and only then the Windows crash requester shows up. Since I have already waited for it once (and reported the content here), now when CB freezes I suddently close it the hard way to avoid waiting. Next time I will wait to see if a .rpt can still generated or not (but I fear not)

blauzahn:
Does it happen as well when you disable the code-completion plugin or even startup codeblocks with the command-line argument --safe-mode? Opening and editing a file works even in safe-mode.

If you can start cb from within gdb, then when it becomes unresponsive, please press Ctrl-C. If one function consumes the majority of time, chances are that it breaks in that function. Issuing within gdb the command backtrace might give you the corresponding backstrace to that function. Finding a solution is another story, of course.


Elena:
Fact is, since the problem happens very seldom (sometimes even once monthly), it would be very impractical for me to launch CB from the command line everytime instead of launching it from a project. Clearly if the bug was easily replicable I could surely do that...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version