Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: JSeglem on January 03, 2015, 05:38:57 pm

Title: Changing font size causes crash on Mac Yosemite
Post by: JSeglem on January 03, 2015, 05:38:57 pm
I have tried to increase the font size via Settings/Editor then select "Choose" which takes me to the font window. The numerous times I have tried to increase the size of the font Codeblocks instantly crashes.

This may be overkill, but I've attached the problem report that pops up.

Is this a bug? Or am I doing something wrong?



[attachment deleted by admin]
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: oBFusCATed on January 03, 2015, 11:47:24 pm
I think it is a bug, and it is reported many times but we have no active osx developer which can fix it. We need volunteers...
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: Jenna on January 04, 2015, 12:29:54 am
Which version of C::B do you use ?
If I remember correctly, it' a wxWidgets bug.
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: JSeglem on January 04, 2015, 06:45:23 pm
Thanks for responses. I usually don't have an issue with font size, but I find when I looking for things like ; or ' the font size makes them hard to spot.

I'm new to this and downloaded the Release 13.12 rev 0 gcc 4.2.1 Mac OS x/unicode 32 bit.

Will hope the bug gets resolved when a resource shows up.
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: pdtl on May 18, 2015, 06:07:59 pm
Hi all - I just wanted to follow up on this post, which I found while having the same problem.

A workaround that I have used is to edit the default.conf file found at:

/Users/<User>/Library/Application Support/codeblocks/default.conf

and change the following line:

<FONT>
        <str>
                <![CDATA[0;10;75;90;90;0;Monaco;0]]>
   </str>
</FONT>

change the "10" to the font size you want. It takes a little trial and error to find the right size (I found that 12 is good for me). Make sure that Code::Blocks is closed when editing this file or your changes will be overwritten when closing the program.

Hope this helps!
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: rafael.zemog on July 12, 2015, 06:46:51 pm
I can test CB on MAC OS Yosemite
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: afb on July 13, 2015, 03:05:43 pm
Quote from: rafael.zemog on July 12, 2015, 06:46:51 pm
I can test CB on MAC OS Yosemite
You will probably also need a debug build (with symbols) of both wxWidgets and Code::Blocks...

Anyway here is the stacktrace:
Code
Performing @selector(_chooseSizeFromList:) from sender NSFontPanelTableView 0x132a1ff0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x900ce69a __pthread_kill + 10
1   libsystem_pthread.dylib       	0x9105ff19 pthread_kill + 101
2   libsystem_c.dylib             	0x921a6eee abort + 156
3   libwx_macu-2.8.dylib          	0x003a7ff5 wxFatalSignalHandler + 37
4   libsystem_platform.dylib      	0x976ee03b _sigtramp + 43
5   ???                           	0xffffffff 0 + 4294967295
6   libwx_macu-2.8.dylib          	0x003a7fd0 wxHandleFatalExceptions(bool) + 400
7   libwx_macu-2.8.dylib          	0x003de982 wxFont::Unshare() + 66
8   libwx_macu-2.8.dylib          	0x003ddf93 wxFont::SetFaceName(wxString const&) + 19
9   libwx_macu-2.8.dylib          	0x003df3f0 wxMacCarbonFontPanelHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 352
10  com.apple.HIToolbox           	0x915895a4 _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36

https://github.com/wxWidgets/wxWidgets/blob/WX_2_8_BRANCH/src/mac/carbon/font.cpp
Title: Re: Changing font size causes crash on Mac Yosemite
Post by: afb on July 13, 2015, 03:12:39 pm
Note that you cannot use Xcode 4 or later to build the 32-bit target (wxMac).
So you need access to Xcode 3.2.6 and the old MacOSX10.6.sdk to build this...

All new OS X development needs to target wxWidgets 3 instead, for 64-bit support.
Then you will have new interesting issues with wxOSX, instead of these old ones.