News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

The 22 March 2014 build (9744) is out.

Started by killerbot, March 28, 2014, 09:39:02 PM

Previous topic - Next topic

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 22 March 2014 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20140322_rev9744_win32.7z
  - Linux :
   none

Resolved Fixed:


  • debugger: Disable deleting of Locals and Function arguments watches with the Delete key
  • lots of CC Manager changes
  • editor: swap header/source, if nothing else worked, search for auto-generated by file
  • compiler: Make building/cleaning custom makefile projects more verbose, so users can have a chance to see what commands are executed

Regressions/Confirmed/Annoying/Common bugs:




dmoore

My nightly Ubuntu PPA building now (will try to keep up with this again)
Python plugins: [url="https://github.com/spillz/codeblocks-python"]https://github.com/spillz/codeblocks-python[/url]
Code::Blocks Daily Builds -- Ubuntu PPA: [url="https://launchpad.net/~damien-moore/+archive/codeblocks"]https://launchpad.net/~damien-moore/+archive/codeblocks[/url]

Jenna

On my server since some hours:

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 (fc19, fc20 and rawhide) and RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) can be found in my rpm-repo .

No fc18 packages any more (removed from mock due to end of live).

carra

Up and running under Windows. The new CC pop ups with information about identifiers are really useful! Cool work, guys  ;D

vwdvaan

Crash ;) on Win 7 x32:

codeblocks.exe caused an Access Violation at location 006ccc1f Reading from location 006ccc1f.

Registers:
eax=006ccc1f ebx=0000001c ecx=0747e2d8 edx=00000000 esi=004dd828 edi=00000000
eip=006ccc1f esp=0022f7d8 ebp=0022f9a4 iopl=0         nv up ei pl nz ac pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010212

Call stack:
006CCC1F
6CD111EE  wxmsw28u_gcc_cb.dll:6CD111EE  _ZN8wxWindow13MSWWindowProcEjjl
6CD0ADAE  wxmsw28u_gcc_cb.dll:6CD0ADAE  _Z9wxWndProcP6HWND__jjl@16
7758C4E7  USER32.dll:7758C4E7  gapfnScSendMessage
7758C5E7  USER32.dll:7758C5E7  gapfnScSendMessage
77584F0E  USER32.dll:77584F0E  GetScrollBarInfo
77584F7D  USER32.dll:77584F7D  GetScrollBarInfo
7773702E  ntdll.dll:7773702E  KiUserCallbackDispatcher
6CCEFA40  wxmsw28u_gcc_cb.dll:6CCEFA40  _ZN11wxEventLoop8DispatchEv


Latest working copy for me was svn9677.
Win 10, MinGW 122.0, wxWidgets 3.1.7

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

damorin

Hi,

got something similar (see attached report file).

Project Test project' parsing stage done (952 total parsed files, 8954 tokens in 0 minute(s), 0.015 seconds).
ClassBrowser::OnThreadEvent(): Updating class browser...
ClassBrowser::OnThreadEvent(): Class browser updated.
Re-parsed 1 files.
Can't find compiler executable in your configured search path's (for MingW32)...
Can't find compiler executable in your configured search path's (for MingW32)...
Segmentation fault
/cygdrive/c/...iles/codeblocks $
One problem at a time and we will get there.

vwdvaan

Quote from: oBFusCATed on March 31, 2014, 02:07:21 PM
Any steps to reproduce this crash?
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...

BOOM!!!  :D

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

Call stack:
BC68551C
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
00402922  codeblocks.exe:00402922
684F1D1C  wxmsw28u.dll:684F1D1C  _Z7wxEntryP11HINSTANCE__S0_Pci
00401D00  codeblocks.exe:00401D00
004010FD  codeblocks.exe:004010FD
77BA37EB  ntdll.dll:77BA37EB  RtlInitializeExceptionChain
77BA37BE  ntdll.dll:77BA37BE  RtlInitializeExceptionChain


I think that the error was introduced in latest commits with new CC plugin.
Win 10, MinGW 122.0, wxWidgets 3.1.7

ToApolytoXaos

Quote from: jens on March 29, 2014, 11:26:54 PM
On my server since some hours:

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 (fc19, fc20 and rawhide) and RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) can be found in my rpm-repo .

No fc18 packages any more (removed from mock due to end of live).
jens, after many attempts to compile codeblocks on my debian testing 64-bit, i gave up. the issue was beyond my limited knowledge as of why it would crash and decided to use your nightly builds. I have finally found my piece!

Thank you so much for your amazing work. I wish I knew how you managed to make it work :/

Alpha

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...
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?

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...
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?
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?
Win 10, MinGW 122.0, wxWidgets 3.1.7

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?
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
....
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?
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

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?
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
....
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?

:)
Recompiled with -g -O0 for cb_release_type and no break or detailed threads in Call stack.

Running standalone and intercepted with Dr. MinGW:

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


Win 10, MinGW 122.0, wxWidgets 3.1.7

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..
Windoze 8.1 x86_64 16GiB RAM, wxWidgets-2.8x (latest,trunk), MinGW-builds (latest, posix-threads)
Code::Blocks (x86 , latest , selection length patch , build option fixes/additions , toggle comments)

Miguel Gimenez

#14
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:


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?)


Compiled with gcc 4.7.0 (MinGW) and wxWidgets 2.8.12

HTH