The 25 January 2014 build (9605) is out.

[killerbot]

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2812_gcc481-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc481-TDM.7z

The 25 January 2014 build is out.
 - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20140125_rev9605_win32.7z
 - Linux :
   none

Resolved Fixed:

• too much to list

Regressions/Confirmed/Annoying/Common bugs:

[killerbot]

IMPORTANT : SWITCHED TO TDM-GCC 4.8.1 ==> re-download mingw and wx dll.

[dmoore]

rev9605 Nightly for Ubuntu versions 12.04 and later (i386 and AMD64) are building now: see https://code.launchpad.net/~damien-moore/+recipe/codeblocks-nightly
Link to the Nightly PPA is in my sig

[Jenna]

As usual (and most of the time updated more frequently):

Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc18, fc19, fc20 and rawhide) and RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) can be found in my rpm-repo .

[shurick]

Packages for openSUSE 12.2 - 13.1 (binaries and sources) for 32-bit and 64-bit.

[damorin]

Hi,

Just installed it (and the mingw10.dll) in my Windows XP (over the RC2) but CodeBlocks didn't go far and stalled in the "Start Here" taking 50% of the CPU time (but no i/o actitivites).

I started CodeBlocks with -v and the result is in the attached fie.

With -v -d, CodeBlocks is showing a dialog box name "CodeBlocks error" but nothing in it.

When I run it in safe mode, I'm able to go forward and CodeBlock seems to run properly.

Damorin

[Jenna]

Hi,

Just installed it (and the mingw10.dll) in my Windows XP (over the RC2) but CodeBlocks didn't go far and stalled in the "Start Here" taking 50% of the CPU time (but no i/o actitivites).

I started CodeBlocks with -v and the result is in the attached fie.

With -v -d, CodeBlocks is showing a dialog box name "CodeBlocks error" but nothing in it.

When I run it in safe mode, I'm able to go forward and CodeBlock seems to run properly.

Damorin

Did you also install the wxWidgets-dll built with TDM's MinGW 4.8 ?

[damorin]

Duh...

Shame on me, I missed that, now it's OK.

Thanks.

[ToApolytoXaos]

Current compiled version: svn9613
Compiler: TDM's GCC 4.8.1 32-bit
OS: Windows 7 Enterprise 64-bit
GUI Framework: wxMSW-2.8.12 (32-bit)

Current issue: mouse scroller does not work on auto-completion's pop up window; only arrows up and down.

A possible bug? Cheers.

[Alpha]

Current issue: mouse scroller does not work on auto-completion's pop up window; only arrows up and down.

This is a limitation of the Windows operating system.  If you feel adventuresome, you could try the cc_interface branch (which contains a workaround).

[ToApolytoXaos]

This is a limitation of the Windows operating system.  If you feel adventuresome, you could try the cc_interface branch (which contains a workaround).

It's OK; I can live without this lol thank you for your suggestion.

[jeffsturmann]

Where i can find the bugs fixed list? I want know if the issue with the code completion to C++11 features was fixed or not  ??? :-\

[dmoore]

Where i can find the bugs fixed list? I want know if the issue with the code completion to C++11 features was fixed or not  ??? :-\

Browse the SVN log: http://sourceforge.net/p/codeblocks/code/9614/log/?path=

(But from what I've read, it sounds like full C++ 11 support is a long way off)

[ToApolytoXaos]

How stable Code::Blocks built with wxGTK 3.0 is? I built it on debian testing (jessie), 64-bit using GCC 4.8.2 and caused for once again those useful asserting error messages:

Code Select Expand


ASSERT INFO:
../src/common/wincmn.cpp(1517): assert "Assert failure" failed in RemoveEventHandler(): where has the event handler gone?

BACKTRACE:
[1] wxWindowBase::RemoveEventHandler(wxEvtHandler*)
[2] wxBinderEvtHandler::~wxBinderEvtHandler()
[3] wxBinderEvtHandler::~wxBinderEvtHandler()
[4] wxKeyBinder::DetachAll()
[5] wxKeyProfileArray::DetachAll()
[6] cbKeyBinder::OnRelease(bool)
[7] cbPlugin::Release(bool)
[8] PluginManager::DetachPlugin(cbPlugin*)
[9] PluginManager::UnloadPlugin(cbPlugin*)
[10] PluginManager::UnloadAllPlugins()
[11] PluginManager::~PluginManager()
[12] PluginManager::~PluginManager()
[13] Mgr<PluginManager>::Free()
[14] Manager::Shutdown()
[15] MainFrame::OnApplicationClose(wxCloseEvent&) /home/stefanos/svn_code/CodeBlocks/src/src/main.cpp:2755
[16] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const
[17] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[18] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[19] wxEvtHandler::TryHereOnly(wxEvent&)
[20] wxEvtHandler::DoTryChain(wxEvent&)
[21] wxEvtHandler::ProcessEvent(wxEvent&)
[22] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[23] wxWindowBase::Close(bool)
[24] MainFrame::OnFileQuit(wxCommandEvent&) /home/stefanos/svn_code/CodeBlocks/src/src/main.cpp:2655
[25] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const
[26] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[27] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[28] wxEvtHandler::TryHereOnly(wxEvent&)
[29] wxEvtHandler::DoTryChain(wxEvent&)
[30] wxEvtHandler::ProcessEvent(wxEvent&)
[31] wxWindowBase::TryAfter(wxEvent&)
[32] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[33] wxMenuBase::SendEvent(int, int)
[34] g_closure_invoke
[35] g_signal_emit_valist
[36] g_signal_emit
[37] gtk_widget_activate
[38] gtk_menu_shell_activate_item
[39] g_closure_invoke
[40] g_signal_emit_valist
[41] g_signal_emit
[42] gtk_propagate_event
[43] gtk_main_do_event
[44] g_main_context_dispatch
[45] g_main_loop_run
[46] gtk_main
[47] wxGUIEventLoop::DoRun()
[48] wxEventLoopBase::Run()
[49] wxAppConsoleBase::MainLoop()
[50] CodeBlocksApp::OnRun() /home/stefanos/svn_code/CodeBlocks/src/src/app.cpp:809
[51] wxEntry(int&, wchar_t**)
[52] main /home/stefanos/svn_code/CodeBlocks/src/src/app.cpp:276
[53] __libc_start_main
[54] _start


Program received signal SIGSEGV, Segmentation fault.
0x0000000000000030 in ?? ()
(gdb) bt
#0  0x0000000000000030 in ?? ()
#1  0x00007ffff605921f in ~wxEventTableEntryBase (this=0x7ffff62f1b20 <wxTreeListCtrl::sm_eventTableEntries>, __in_chrg=<optimized out>)
   at ../include/wx/event.h:3177
#2  ~wxEventTableEntry (this=0x7ffff62f1b20 <wxTreeListCtrl::sm_eventTableEntries>, __in_chrg=<optimized out>) at ../include/wx/event.h:3196
#3  __tcf_0 () at ../src/generic/treelist.cpp:987
#4  0x00007ffff1a58e2f in __cxa_finalize (d=0x7ffff62eefc0) at cxa_finalize.c:55
#5  0x00007ffff5fec723 in __do_global_dtors_aux () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#6  0x00007fffffffe2f0 in ?? ()
#7  0x00007ffff7de9fcf in _dl_fini () at dl-fini.c:253
Backtrace stopped: frame did not save the PC

(gdb) continue
Continuing.

Program received signal SIGABRT, Aborted.
0x00007ffff1a541d5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.


What made me realize something went wrong was the lightning speed it closed the entire IDE. I run it within terminal and saw an "aborted" message upon plugin deinitialization.

Then I run it through GDB to detect the bug...and there it would start spitting various assert() messages; about missing *.xrc files, then about messages isOK() and so forth.

[oBFusCATed]

How stable Code::Blocks built with wxGTK 3.0 is?

At the moment it should be used by people willing to provide patches with fixes!