Code::Blocks quits unexpectedly on OS X

[Neal M]

Hi all,

I'm a total n00b, hopefully this is the correct place to ask this question (please advise if it is not):

I'm running Code::Blocks 13.12 on OS X 10.13.2 (MacBook Pro, 2014), and every so often, for no apparent reason C::B spontaneously quits. I can restart the program of course, but it's pretty annoying.

I did note on the download page that the OS X version hasn't been maintained much if at all over the last while, so that's my first guess as to why. But my question is what, if anything I can do about it?

Would downloading the source code and compiling it on my system lead to any improvement over the binary that was presumably compiled on an older OS X version, or would that just be a waste of time? Maybe at some point I will have the skills to actually fix the Mac version, but right now I can barely code a command line calculator.

Thanks in advance.

[oBFusCATed]

You can build the trunk version, but I'm not sure it will solve your problem.
But I'll be happy to try to fix it if you can make it crash every time or post the call stack.

On macOS when something there are pretty good reports. Do you see a dialog with a crash report?

p.s. Unfortunately there is no macOS dev using it often to fix all macOS related problems.

[Neal M]

It does usually show me a crash report, but reproducing the event is going to be tricky as it seems to happen randomly, or at least without relation to any specific user action. I'll post the call stack next time a crash occurs.

[Neal M]

Here's the crash report:

[oBFusCATed]

Can you try to disable the Symbol browser in the Code completion plugin settings and see if this crash goes away?

[Neal M]

I will try, thanks.

[oBFusCATed]

Did it fix the problem?

[Neal M]

So far so good. It seems to not be crashing.

I'll assume that that did the trick, and post back here if the issue returns.

Thanks for your help!

[hidefromkgb]

Oh, cool! Been experiencing the same thing; at times it gets very frustrating.
Thank you for the workaround.

[oBFusCATed]

In the night builds topics there are posts with links to newer osx releases. Probably you can consider them...