ASSERT INFO:
../include/wx/dynarray.h(838): assert "uiIndex < m_nCount" failed in Item().
BACKTRACE:
[1] wxGenericTreeCtrl::CalculateLevel(wxGenericTreeItem, wxDC&, int, int&)
[2] wxGenericTreeCtrl::CalculatePositions()
[3] wxGenericTreeCtrl::DoDirtyProcessing()
[4] wxGenericTreeCtrl::OnInternalIdle()
[5] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[6] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[7] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[8] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[9] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[11] wxFrame::SendIdleEvents(wxIdleEvent&)
[12] wxAppBase::ProcessIdle()
[13] wxApp::DoIdle()
[14] g_main_context_dispatch
[15] g_main_loop_run
[16] gtk_main
[17] wxGUIEventLoop::DoRun()
[18] wxEventLoopBase::Run()
[19] wxAppConsoleBase::MainLoop()
[20] CodeBlocksApp::OnRun() /home/zfmgpu/Desktop/Repository/codeblocks/trunk/src/src/app.cpp:852
[21] wxEntry(int&, wchar_t*)
[22] main /home/zfmgpu/Desktop/Repository/codeblocks/trunk/src/src/app.cpp:322
[23] __libc_start_main
[24] _start
Suddenly appears, in 10507
What do I need to do to reproduce this problem?
Huch, hard to say,
it appears (both submittet errors by me) when opening new files not yet
open in the editor
Could it be related to old configured (cmake) projects and their layout
files? I completely deleted the build folder of my projects and made new
ones which I opened in the SVN codeblock version...
I deleted also .config/codeblocks folder to make sure no confusion
arises hopefully, when migrating from ubuntu to the SVN compiled version.
( could it happen that codeblocks mixes wxwidget 2.8 and 3.0 during
compilation? not really right? that would be noticed?
Thanks!
Last edit: ollydbg 2015-09-28
You can check this by using lsof -p
pidof codeblocks
| grep wx. If both wx28 and wx30 are loaded then your build is broken.But my guess is that you've found a bug in the wx30 builds that should be fixed.
If I can reproduce it then I can easily fix it, I hope.
I am trying, 3.0.2 wxwidget bild right now, to see if the error still happen
Ok the errors, still persist even with the unofficial wxwidgets from codelite (3.0.2)
Teodor, is there a revision which uses the wx2.8? which one should i checkout in svn?
Thanks!
Or can codeblocks (latest revision) be built with 2.8?
We don't store binaries in svn, so there is no revision built with 2.8 there, only source code.
You have to build it yourself and yes wx2.8 is supported (in fact this is the more stable way to build cb).
Can you describe the minimal steps need so I can reproduce the problem? Minimal example project, etc.
Hehe , of course :-), I just realized, an built codeblocks with wx2.8 instead of wx3.0 ( you dont have version numbers or tags in the svn?) dont know
I will see if I can extract a minimal example project when I have time,
Did you see this error already? or never experienced problems with wx 3.0?
So the error is deep inside the wxwidget loops somewhere…
Thanks :-)
Related
Tickets:
#225We have tags and branches for releases.
I'm not using wx30, because it is too unstable, but I'm trying to fix as many problems reported about it.
FYI: This issue is caused by the Symbol Browser. Disable it and you won't see such crashes. The symbol browser should be re-written, because it is executing wx gui code from non-main threads. The option to disabled it is somewhere in the code completion settings.
Has a backtrace from the worker thread http://forums.codeblocks.org/index.php/topic,20833.msg142279/topicseen.html#msg142279
This is giving me fits because the symbol browser is enabled by default and I sometimes forget to disable it after starting. The symptom varies, most often something like this
Error in `codeblocks': corrupted double-linked list: 0x01b19cf0
I am running Raspbian and installed codeblocks using apt-get. This the first editor I have used in years that will crash and lose work. I hope someone is working on this.
In 17.12 it is not enabled by defualt , just update to the latest version... We cannot do much else at this point about it.
Hi, Can you please check if the issue is still occurring in Code::Blocks 20.03 and post here if it is fixed or not. The CB 20.03 download page is https://www.codeblocks.org/downloads/binaries/.
If you are using Windows 64 bit and 20.03 and the issue is still occurring you could try the latest nightly and post here if the issue occurs or not in the nightly, which can be found in the following CB forum https://forums.codeblocks.org/index.php/board,20.0.html .
The symbol browser is completely disabled in 20.03, so it can't fail there. It was reworked and reenabled about six months ago, and it no longer calls the main thread from the worker one, so this ticket can be closed.