User forums > Nightly builds
The 22 March 2014 build (9744) is out.
vwdvaan:
--- Quote from: Alpha on April 01, 2014, 02:58:53 pm ---
--- Quote from: vali29 on April 01, 2014, 09:50:54 am ---1) Open Notepad
2) Open Codeblocks with a test project and check "Display info when hovering mouse over a token in the editor" from Settings->Editor->Code completion->Code completion
3) Put the mouse cursor over a token in editor and let to apear the little pop-up with description.
4) Now click on Notepad window...
--- End quote ---
Under Windows 7 x64, this does not crash for me (both self compiled, and prebuilt nightly). Is there anything non-standard about the configuration of your machine?
--- End quote ---
Hi Alpha!
I don't know what is a non-standard configuration.
I have svn 9677 compiled by me and it's working very well.
Both svn 9677 and svn 9744 have the same settings and the same plugins.
Do you know how to catch a more complex debug message from CodeBlocks?
ollydbg:
--- Quote from: vali29 on April 01, 2014, 03:50:09 pm ---Do you know how to catch a more complex debug message from CodeBlocks?
--- End quote ---
Can you start the C::B from debugger(I mean debug C::B under C::B), and if it crashed, you can see a full call stack about every thread.
From what I see in your call-stack
--- Quote ---codeblocks.exe caused an Access Violation at location bc68551c Reading from location bc68551c.
Registers:
eax=bc68551c ebx=00000d88 ecx=071398a8 edx=00000000 esi=071398a8 edi=00000d88
eip=bc68551c esp=0022f548 ebp=0022f9c4 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010216
....
--- End quote ---
I can not guess any thing related to CC. :)
I think it is better you can share us a test project, so we can test it on our system.
BTW: you say "Notepad" means Editor window of C::B?
vwdvaan:
--- Quote from: ollydbg on April 01, 2014, 04:29:44 pm ---
--- Quote from: vali29 on April 01, 2014, 03:50:09 pm ---Do you know how to catch a more complex debug message from CodeBlocks?
--- End quote ---
Can you start the C::B from debugger(I mean debug C::B under C::B), and if it crashed, you can see a full call stack about every thread.
From what I see in your call-stack
--- Quote ---codeblocks.exe caused an Access Violation at location bc68551c Reading from location bc68551c.
Registers:
eax=bc68551c ebx=00000d88 ecx=071398a8 edx=00000000 esi=071398a8 edi=00000d88
eip=bc68551c esp=0022f548 ebp=0022f9c4 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010216
....
--- End quote ---
I can not guess any thing related to CC. :)
I think it is better you can share us a test project, so we can test it on our system.
BTW: you say "Notepad" means Editor window of C::B?
--- End quote ---
:)
Recompiled with -g -O0 for cb_release_type and no break or detailed threads in Call stack.
Running standalone and intercepted with Dr. MinGW:
--- Code: ---codeblocks.exe caused an Access Violation at location 4cb22a68 Reading from location 4cb22a68.
Registers:
eax=4cb22a68 ebx=00000ad4 ecx=11a5ba18 edx=00000000 esi=11a5ba18 edi=00000ad4
eip=4cb22a68 esp=0022f518 ebp=0022f994 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210216
Call stack:
4CB22A68
6852EC49 wxmsw28u.dll:6852EC49 _ZN8wxWindow13MSWWindowProcEjjl
68527BA0 wxmsw28u.dll:68527BA0 _Z9wxWndProcP6HWND__jjl@16
775EC4E7 USER32.dll:775EC4E7 gapfnScSendMessage
775EC5E7 USER32.dll:775EC5E7 gapfnScSendMessage
775E4F0E USER32.dll:775E4F0E GetScrollBarInfo
775E4F7D USER32.dll:775E4F7D GetScrollBarInfo
77B8702E ntdll.dll:77B8702E KiUserCallbackDispatcher
68511E35 wxmsw28u.dll:68511E35 _ZN11wxEventLoop8DispatchEv
6858B3B2 wxmsw28u.dll:6858B3B2 _ZN17wxEventLoopManual3RunEv
685724D0 wxmsw28u.dll:685724D0 _ZN9wxAppBase8MainLoopEv
00405B8E codeblocks.exe:00405B8E CodeBlocksApp::OnRun app.cpp:818
...
try
{
> int retval = wxApp::OnRun();
// wx 2.6.3 docs says that OnRun() function's return value is used as exit code
return m_Batch ? m_BatchExitCode : retval;
...
684A9954 wxmsw28u.dll:684A9954 _Z14wxUninitializev
684F1D1C wxmsw28u.dll:684F1D1C _Z7wxEntryP11HINSTANCE__S0_Pci
00401DD6 codeblocks.exe:00401DD6 WinMain@16 app.cpp:278
...
} // namespace
> IMPLEMENT_APP(CodeBlocksApp) // TODO: This gives a "redundant declaration" warning, though I think it's false. Dig through macro and check.
BEGIN_EVENT_TABLE(CodeBlocksApp, wxApp)
...
0050074B codeblocks.exe:0050074B _ZNK8cbPlugin9CanDetachEv
004010FD codeblocks.exe:004010FD
77BA37EB ntdll.dll:77BA37EB RtlInitializeExceptionChain
77BA37BE ntdll.dll:77BA37BE RtlInitializeExceptionChain
--- End code ---
White-Tiger:
I still wonder why it seems like you guys never got a crash.. my CB is crashing since the CC changes... and it crashes just after a few minutes running... Crashes while writing code, while scrolling, while compiling... actually at every single moment a crash can happen...
That's why I'm using my stable #9673 :P
But yeah... debugging CB on Windows is a pain... best is indeed to debug it with CB itself... or to attach gdb manually...
but even a backtrace on all threads (t a a bt full) using gdb after a crash or while a freeze gives almost no information... my CB is currently >1GiB in size because I've increased debugging output to maximum..
Miguel Gimenez:
I've the same problem than Vali29. I'm using SVN9744 (self compiled) over Windows XP SP3, and if you remove focus from Codeblocks when CC is showing the tip you always get a segmentation fault.
Debuging within Codeblocks or within gdb alone shows the same results: the backtrace is truncated to two (sometimes three) lines. Using gdb:
--- Code: ---Program received signal SIGSEGV, Segmentation fault.
0x00002265 in ?? ()
(gdb) bt
#0 0x00002265 in ?? ()
#1 0x627a190d in ?? ()
#2 0x003f0450 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--- End code ---
Compiled with gcc 4.7.0 (MinGW) and wxWidgets 2.8.12
HTH
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version