Author Topic: The 08 February 2014 build (9639) is out.  (Read 38697 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5193
The 08 February 2014 build (9639) is out.
« on: February 08, 2014, 03:39:39 pm »
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 08 Feb 2014 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20140208_rev9639_win32.7z
  - Linux :
   none

Resolved Fixed:

  • editor: Add keywords for ruby 1.9, this fixes the Ruby lexer
  • new command line option --user-data-dir=<path> to specify an alternative directory for user settings and user installed plugins
  • debugger: Determine console pid from ps-command, returns either the same as we have now (e.g. xterm) or the pid of the sleep-command and works therefore also with newer gnome-terminals (thanks Jens)
  • debugger: Rework RunNixConsole to be even simpler, the old version always printed an error message and return the pid of the sleep command
  • debugger: Try to detect when the terminal couldn't be started and print an error instead of entering annoying loop
  • single file compilation: fix a crash if user selects a wrong target
  • CC: fix a bug (logic error) introduced in rev 9601

Regressions/Confirmed/Annoying/Common bugs:



    Offline maryjeck

    • Single posting newcomer
    • *
    • Posts: 5
    Re: The 08 February 2014 build (9639) is out.
    « Reply #1 on: February 09, 2014, 11:43:16 am »
    There must be something wrong with it。

    When I open an Project.
    There are lost a word like like this "NativeParser::OnParserEnd(): Project '******' parsing stage done!".

    and I can do nothing with it,it FC.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 08 February 2014 build (9639) is out.
    « Reply #2 on: February 09, 2014, 11:56:06 am »
    There must be something wrong with it。

    When I open an Project.
    There are lost a word like like this "NativeParser::OnParserEnd(): Project '******' parsing stage done!".

    and I can do nothing with it,it FC.
    Where do you see this messages ?
    Can you provide a sample (minimal) workspace/project where this occurs ?

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 08 February 2014 build (9639) is out.
    « Reply #3 on: February 09, 2014, 11:57:16 am »
    As usua:

    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 .

    Offline shurick

    • Multiple posting newcomer
    • *
    • Posts: 35
    Re: The 08 February 2014 build (9639) is out.
    « Reply #4 on: February 09, 2014, 02:03:15 pm »
    Packages for openSUSE 12.2 - 13.1 (binaries and sources) for 32-bit and 64-bit.
    Packages for openSUSE http://codeblocks.esy.es  (binaries and sources) for 32-bit and 64-bit.

    Offline dmoore

    • Developer
    • Lives here!
    • *****
    • Posts: 1576
    Re: The 08 February 2014 build (9639) is out.
    « Reply #5 on: February 09, 2014, 03:18:42 pm »
    Ubuntu packages building here

    Offline damorin

    • Multiple posting newcomer
    • *
    • Posts: 40
    Re: The 08 February 2014 build (9639) is out.
    « Reply #6 on: February 09, 2014, 05:11:00 pm »
    Hi,

    something new in this release. Each time I try "Find functions calling <x>", CSCOPE crash.

    I noticed the cscope database "cscope.out" have been renamed "ncscope.out".

    Renaming it to the original name is fixing the problem.

    I'm using cscope v15.7a



    One problem at a time and we will get there.

    Offline maryjeck

    • Single posting newcomer
    • *
    • Posts: 5
    Re: The 08 February 2014 build (9639) is out.
    « Reply #7 on: February 10, 2014, 03:46:16 am »
    There must be something wrong with it。

    When I open an Project.
    There are lost a word like like this "NativeParser::OnParserEnd(): Project '******' parsing stage done!".

    and I can do nothing with it,it FC.
    Where do you see this messages ?
    Can you provide a sample (minimal) workspace/project where this occurs ?

    build(9619):
    The message is like this:
    NativeParser::CreateParser(): Finish creating a new parser for project '***********'
    NativeParser::OnParserEnd(): Project '********' parsing stage done!

    build(9639):
    like this:
    NativeParser::CreateParser(): Finish creating a new parser for project '***********'

    Only one word.

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5247
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 08 February 2014 build (9639) is out.
    « Reply #8 on: February 10, 2014, 04:35:08 am »
    There must be something wrong with it。

    When I open an Project.
    There are lost a word like like this "NativeParser::OnParserEnd(): Project '******' parsing stage done!".

    and I can do nothing with it,it FC.
    Where do you see this messages ?
    Can you provide a sample (minimal) workspace/project where this occurs ?

    build(9619):
    The message is like this:
    NativeParser::CreateParser(): Finish creating a new parser for project '***********'
    NativeParser::OnParserEnd(): Project '********' parsing stage done!

    build(9639):
    like this:
    NativeParser::CreateParser(): Finish creating a new parser for project '***********'

    Only one word.
    Ok, so it looks like the CC's parser hangs or go to some infinite loop.
    If you see the change between rev 9619 and 9639, there are few CC related changed.

    Code: [Select]
    Revision: 9639
    Author: ollydbg
    Date: 2014-2-8 17:33:14
    Message:
    - CC: use wx_str() instead of c_str().
    -------------------------------
    M(T ) : /trunk/src/plugins/codecompletion/nativeparser.cpp

    Revision: 9638
    Author: ollydbg
    Date: 2014-2-8 17:32:33
    Message:
    * CC: fix a bug (logic error) introduced in rev 9601.
    -------------------------------
    M(T ) : /trunk/src/plugins/codecompletion/parser/tokenizer.cpp


    Revision: 9636
    Author: fuscated
    Date: 2014-2-4 7:15:50
    Message:
    - CC: Make the code a bit more readable
    -------------------------------
    M(T ) : /trunk/src/plugins/codecompletion/parser/parserthread.cpp

    Revision: 9635
    Author: fuscated
    Date: 2014-2-4 7:15:45
    Message:
    - wx30: Fix a format specifier mismatch assert
    -------------------------------
    M(T ) : /trunk/src/plugins/codecompletion/parser/parserthread.cpp


    I guess the change of rev9638 (* CC: fix a bug (logic error) introduced in rev 9601.) cause this bug. But in-fact rev 9638 is going fix a logic error, so another guess is that rev 9601 does not truly fix the bug.

    I would welcome a test project/workspace. Meanwhile, I will re-test the sample project in this discussion:  NativeParser lockup when parsing Visual Studio 2013 and Boost 1.55.0 headers later today.

    EDIT:
    Code blocks using too much cpu, this contains a sample project which will lead to hang issue.
    « Last Edit: February 10, 2014, 04:51:32 am by ollydbg »
    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.

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5247
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 08 February 2014 build (9639) is out.
    « Reply #9 on: February 10, 2014, 04:53:51 am »
    ...
    I would welcome a test project/workspace. Meanwhile, I will re-test the sample project in this discussion:  NativeParser lockup when parsing Visual Studio 2013 and Boost 1.55.0 headers later today.

    EDIT:
    Code blocks using too much cpu, this contains a sample project which will lead to hang issue.
    FYI: I test the sample project in above link with C::B rev 9643, I can't find see the hang issue here. So, I definitely need a reproducer, thanks.
    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.

    Offline grf

    • Multiple posting newcomer
    • *
    • Posts: 12
    Re: The 08 February 2014 build (9639) is out.
    « Reply #10 on: February 10, 2014, 12:40:24 pm »
    After starting CB and opening some projects, the CPU load increases up to 100% and the GUI doesn't react anymore. I tried three different projects: Two projects for programs with GUI (wxWidgets based) and one simple C/C++ project. Only these both projects with wxWidgets lead to this behaviour.

    Offline stahta01

    • Lives here!
    • ****
    • Posts: 6671
      • My Best Post
    Re: The 08 February 2014 build (9639) is out.
    « Reply #11 on: February 10, 2014, 04:34:24 pm »
    After starting CB and opening some projects, the CPU load increases up to 100% and the GUI doesn't react anymore. I tried three different projects: Two projects for programs with GUI (wxWidgets based) and one simple C/C++ project. Only these both projects with wxWidgets lead to this behaviour.

    I am guessing this info might be needed; wxWidgets version, OS name and version, Compiler name and version?

    Are you using Precompiled Headers?

    Tim S.
    C Programmer working to learn more about C++ and Git.
    On Windows 7 64 bit and Windows 10 32 bit.
    On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
    --
    When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

    Offline grf

    • Multiple posting newcomer
    • *
    • Posts: 12
    Re: The 08 February 2014 build (9639) is out.
    « Reply #12 on: February 10, 2014, 06:45:56 pm »
    wxWidgets 3.0.0, no precompiled headers, tdm-gcc 4.7.1-2, Windows XP

    The problem starts directly after loading the project, without any compilation. CB opens the project and then the CPU load goes up to 100% and it doesn't react anymore. After some time I killed it via task manager.
    The nightly svn9619 works without this problem.

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5247
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 08 February 2014 build (9639) is out.
    « Reply #13 on: February 11, 2014, 02:24:53 am »
    wxWidgets 3.0.0, no precompiled headers, tdm-gcc 4.7.1-2, Windows XP

    The problem starts directly after loading the project, without any compilation. CB opens the project and then the CPU load goes up to 100% and it doesn't react anymore. After some time I killed it via task manager.
    The nightly svn9619 works without this problem.
    Can you show a sample/minimal C::B project which cause the hang issue? I'm interest to catch those bugs.  :)
    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.

    Offline grf

    • Multiple posting newcomer
    • *
    • Posts: 12
    Re: The 08 February 2014 build (9639) is out.
    « Reply #14 on: February 11, 2014, 10:14:34 am »
    What I tried is to create a new wxWidgets project, without PCH, a debug configuration (which uses the wxWidgets 3.0.0 release libs) and a release configuration. The project contains no code changes, only the generated files. After opening the project, the CPU load increases up to 100% and CB can only be killed via Task Manager.

    Here is the content of the project file (I don't want to provide any zip archives):

    Code: [Select]
    ?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <CodeBlocks_project_file>
    <FileVersion major="1" minor="6" />
    <Project>
    <Option title="minimal_test" />
    <Option pch_mode="2" />
    <Option compiler="gcc" />
    <Build>
    <Target title="Debug">
    <Option output="bin/minimal_test" prefix_auto="1" extension_auto="1" />
    <Option object_output="bin/" />
    <Option type="0" />
    <Option compiler="gcc" />
    <Option projectLinkerOptionsRelation="2" />
    <Compiler>
    <Add option="-g" />
    <Add directory="C:/Libs/wxWidgets_gcc/lib/gcc_lib/mswu" />
    </Compiler>
    <ResourceCompiler>
    <Add directory="C:/Libs/wxWidgets_gcc/lib/gcc_lib/mswu" />
    </ResourceCompiler>
    <Linker>
    <Add library="libwxmsw30u_core.a" />
    <Add library="libwxbase30u.a" />
    <Add library="libwxpng.a" />
    <Add library="libwxzlib.a" />
    <Add directory="C:/Libs/wxWidgets_gcc/lib/gcc_lib" />
    </Linker>
    </Target>
    <Target title="Release">
    <Option output="bin/minimal_test" prefix_auto="1" extension_auto="1" />
    <Option object_output="bin/" />
    <Option type="0" />
    <Option compiler="gcc" />
    <Option projectLinkerOptionsRelation="2" />
    <Compiler>
    <Add option="-O2" />
    <Add directory="C:/Libs/wxWidgets_gcc/lib/gcc_lib/mswu" />
    </Compiler>
    <ResourceCompiler>
    <Add directory="C:/Libs/wxWidgets_gcc/lib/gcc_lib/mswu" />
    </ResourceCompiler>
    <Linker>
    <Add option="-s" />
    <Add library="libwxmsw30u_core.a" />
    <Add library="libwxbase30u.a" />
    <Add library="libwxpng.a" />
    <Add library="libwxzlib.a" />
    <Add directory="C:/Libs/wxWidgets_gcc/lib/gcc_lib" />
    </Linker>
    </Target>
    </Build>
    <Compiler>
    <Add option="-pipe" />
    <Add option="-mthreads" />
    <Add option="-D__GNUWIN32__" />
    <Add option="-D__WXMSW__" />
    <Add option="-DwxUSE_UNICODE" />
    <Add option="-Wall" />
    <Add directory="C:/Libs/wxWidgets_gcc/include" />
    </Compiler>
    <ResourceCompiler>
    <Add directory="C:/Libs/wxWidgets_gcc/include" />
    </ResourceCompiler>
    <Linker>
    <Add option="-mthreads" />
    <Add library="libkernel32.a" />
    <Add library="libuser32.a" />
    <Add library="libgdi32.a" />
    <Add library="libwinspool.a" />
    <Add library="libcomdlg32.a" />
    <Add library="libadvapi32.a" />
    <Add library="libshell32.a" />
    <Add library="libole32.a" />
    <Add library="liboleaut32.a" />
    <Add library="libuuid.a" />
    <Add library="libcomctl32.a" />
    <Add library="libwsock32.a" />
    <Add library="libodbc32.a" />
    </Linker>
    <Unit filename="minimal_testApp.cpp" />
    <Unit filename="minimal_testApp.h" />
    <Unit filename="minimal_testMain.cpp" />
    <Unit filename="minimal_testMain.h" />
    <Unit filename="resource.rc">
    <Option compilerVar="WINDRES" />
    </Unit>
    <Extensions>
    <code_completion />
    <envvars />
    <debugger />
    <lib_finder disable_auto="1" />
    </Extensions>
    </Project>
    </CodeBlocks_project_file>