EDIT: Don't waste your time stepping through it in the debugger, it will work fine...You're right. But this issue is pretty weird. I placed a fprintf nearly everywhere in the wxAUI code to pinpoint where it got's crashed but so far I can see all my fprintf's. It seems it's not the wxAUI or some deep-level wxWidgets stuff... I also applied some of the "null pointer" patches from the patches on the web page listed in my previous post. This does'nt fix the issue, too. BTW: I believe some of the patches should be applied anyway. Any hints I could use for further investigation?
- if (m_pExamineMemoryDlg)
+ if (!appShutDown && m_pExamineMemoryDlg)
{
CodeBlocksDockEvent evt(cbEVT_REMOVE_DOCK_WINDOW);
evt.pWindow = m_pExamineMemoryDlg;
Manager::Get()->GetAppWindow()->ProcessEvent(evt);
m_pExamineMemoryDlg->Destroy();
}
Anyone out there not using version 2.6.2???Thomas, I've got good news!
Anyone out there not using version 2.6.2???Well, by now I've compiled wxWidgets 2.6.3-RC1. And guess what: It works there, too. I would say that this is proof enough to say that this issue is wxWidgets 2.6.2 related. Furthermore I suggest not putting too much effort into this anymore - sooner or later C::B will work with wxWidgets 2.6.3 (release) anyway...
Didn't fix. :(Which version of wxWidgets you are using? Unicode?! And what are exactly the steps that still cause the crash for you? E.g.: What windo do you undock to where - left/right; besides C::B; completely ouutside / overlapping... maybe you could post a screenshot? Could you try to do the same using wxWidgets 2.6.1?
1. Undock Messages pane (leave Messages pane inside C::B window area).Here at work I did the same steps as yesterday at home and it's still crashing, too. Unfortunately I cannot give a try what happens if I change the lib version here. All I can say is that at home it was crashing, then I compiled C::B from scratch using 2.6.1, then 2.6.3-RC1 and finally 2.6.2 again and there it doesn't crash anymore. Now how strange is that?!
2. Close C::B
3. C::B crash. :(
Hmm I'll wait for 2.6.3 to see if that solves the problem.....