Code::Blocks Forums
User forums => Help => Topic started by: AlisdairM on May 30, 2010, 07:55:45 pm
-
First up I must say thanks for creating such as great piece of software - I wish I was in a better position to contribute but GPL and my day job don't mix well :( [I as using CodeBlocks for my homegrown project of writing a new C++0x STL, but still under work restrictions]
I am also trying to make sense of my new mac - my first non-Windows computer in 20 years! I was hoping CodeBlocks would make the transition simple :)
The first problem I have is that any time I try to change anything under the 'Settings' menu, CodeBlocks crashes when I hit 'OK'.
I *think* the problem is that I cannot find a default.conf file, and suspect there may be issues creating the initial default. If someone could send me a 'vanilla' default.conf suitable for the mac (OSX 10.6.3) and tell me where to put it, I will report back on whether that fixes the problem.
I have a number of other visual issues, probably related to wxWidgets on mac, or on running with a small notebook screen, but I can work around those. Not being able to set up my compiler/environment - that is a blocker right now.
For reference, I have the same problem with 8.02, and was waiting for the new release in case it was simply a matter of outdated binaries for the latest mac OS.
-
The first problem I have is that any time I try to change anything under the 'Settings' menu, CodeBlocks crashes when I hit 'OK'.
Do you have a backtrace ? I don't have Snow Leopard...
For reference, I have the same problem with 8.02, and was waiting for the new release in case it was simply a matter of outdated binaries for the latest mac OS.
There's also the "nightly" builds, between C::B releases:
http://forums.codeblocks.org/index.php/board,20.0.html
http://developer.berlios.de/project/showfiles.php?group_id=5358
-
Not sure what you are asking for - every time it crashes it dumps me into a screen full of info it wants to send to Apple. I suspect this is what you are looking for, but no idea if a local copy is stored. I could copy/paste the text somewhere, but it is probably larger than we want to post in the forum, which also makes me wonder if I am looking at the right thing?
-
Yes, I meant the output of Crash Reporter. Not that useful from a release build,
but it's a start (and debug builds are huge, so we aren't shipping those symbols).
Use http://developer.berlios.de/bugs/?group_id=5358 for reporting and attaching.
See also http://developer.apple.com/mac/library/technotes/tn2004/tn2123.html
-
OK - the full crash log is 102kb, not something to post here.
The top 20 lines of the call-stack from the thread that crashed follow.
What I did to cause this was launch CodeBlocks through the OSX GUI, Select the Settings menu, then Editor.
I changed the tab spacing from 4 to 3, then hit OK --> Boom!
Process: CodeBlocks [65779]
Path: /Users/alisdairmeredith/CodeBlocks/CodeBlocks.app/Contents/MacOS/CodeBlocks
Identifier: org.codeblocks.app
Version: 10.05 (6282)
Code Type: X86 (Native)
Parent Process: launchd [80]
Date/Time: 2010-05-31 16:42:50.621 -0400
OS Version: Mac OS X 10.6.3 (10D573)
Report Version: 6
Interval Since Last Report: 77492 sec
Crashes Since Last Report: 11
Per-App Interval Since Last Report: 11165 sec
Per-App Crashes Since Last Report: 9
Anonymous UUID: 785258E7-5E29-470B-AB52-1CC1EB071A1F
Exception Type: EXC_CRASH (SIGILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libkeybinder.so 0x17a93897 wxKeyBinder::UpdateSubMenu(wxMenu*) + 227
1 libkeybinder.so 0x17a93a1a wxKeyBinder::UpdateAllCmd(wxMenuBar*) + 70
2 libkeybinder.so 0x17a8bfc9 cbKeyBinder::OnKeyConfigDialogDone(MyDialog*) + 261
3 libkeybinder.so 0x17a8c31d MyDialog::OnApply() + 27
4 libcodeblocks.0.dylib 0x00157ff0 EditorConfigurationDlg::EndModal(int) + 9812
5 libwx_macu-2.8.0.dylib 0x007a3982 wxDialogBase::AcceptAndClose() + 64
6 libwx_macu-2.8.0.dylib 0x006ce77e wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) + 108
7 libwx_macu-2.8.0.dylib 0x006ce915 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) + 103
8 libwx_macu-2.8.0.dylib 0x006ced99 wxEvtHandler::ProcessEvent(wxEvent&) + 183
9 libwx_macu-2.8.0.dylib 0x00804e49 wxWindowBase::TryParent(wxEvent&) + 85
10 libwx_macu-2.8.0.dylib 0x006ced4f wxEvtHandler::ProcessEvent(wxEvent&) + 109
11 libwx_macu-2.8.0.dylib 0x006fd0e3 wxControl::ProcessCommand(wxCommandEvent&) + 27
12 libwx_macu-2.8.0.dylib 0x006f899c wxButton::MacControlHit(void*, void*) + 62
13 libwx_macu-2.8.0.dylib 0x007598f3 wxMacWindowControlEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 553
14 libwx_macu-2.8.0.dylib 0x0075a259 wxMacWindowEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 309
15 com.apple.HIToolbox 0x98edc0a9 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
16 com.apple.HIToolbox 0x98edb370 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
17 com.apple.HIToolbox 0x98efdb55 SendEventToEventTarget + 52
18 com.apple.HIToolbox 0x98f4cf7a SendControlHit(HIView*, OpaqueEventRef*, short, unsigned long) + 296
19 com.apple.HIToolbox 0x98f4cdfb HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 45
-
You can try to disable the keybinder plugin. ( Plugins -> Manage plugins...)
Also you could try to remove (backup it first) the C::B's configuration file, there might be something wrong in there...
The file should be somewhere in /Users/alisdairmeredith/CodeBlocks/CodeBlocks.app/ and it is named default.conf.
p.s. backup is needed in order to show the file to the devs, to prevent crashes in the future.
-
The file would be in ~/Library/Application\ Support/CodeBlocks/default.conf
Plugins, however, are in the CodeBlocks.app bundle itself (under Resources).
-
Thanks for the hints - I did not know where to look for the default.config, so now I can edit by hand in the worst case.
In fact, I did not need to do that to get up and running. After disabling the keybinding plug-in, I still got crashes, but could see the call-stack was different, so I disabled *all* plugins. Now I have a stable system, and I have simply re-enabled the compiler plugin so I can execute my code/compile/run-test cycle. This is all I need (personally) for now, although obviously I could do more to try and track down exactly which of the plug-ins is causing the problem.
I will try and track down the troublesome plugins over the next few days and post back as I get more info, in the meantime I now have a productive environment to continue developing my STL that can support the latest GCC 4.6 alpha compiler, which is seriously cool - thanks a lot guys! (Grabbing my GCC compiler via mac-ports, if anyone is curious. So far, 4.6 adds only nullptr for 0x, but that is quite important if you are trying to write an 0x STL!)