Author Topic: The 06 December 2014 build (10050) is out.  (Read 24583 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5179
The 06 December 2014 build (10050) is out.
« on: December 20, 2014, 03:56:13 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://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/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://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/mingwm10_gcc481-TDM.7z

The 06 December 2014 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2014/CB_20141206_rev10050_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:



    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #1 on: December 31, 2014, 08:57:02 am »
    I have noticed a bizarre occurrence...

    I have created a custom File Type association for .vcproj using the other Code::Block entries as a template...
    Quote
    Project File  (MS Visual C++)(v7.0+)
    C:\Dev-CodeBlocks\codeblocks.exe "%1"
    [Open("%1")]
    CODEBLOCKS
    [IfExec_Open("%1")]
    CodeBlocksDDEServer

    It automatically tries to import but doesn't explicitly say so...
    note first since I already have a cbp for notepad2 it asks to confirm overwriting click [OK]

    then it just pops up with the "Compiler selection" small-window,
    so as I have MinGW set to default its auto selected so I just click [OK]....
    next window is the config import window in this case:
    Notepad2
    - Debug   win32
    - Release win32
    I again click [OK]...
    then the confirm overwriting again?! clicks [OK]
    AND asks for Compiler selection AGAIN!?....
    I click ok again and C.R.A.S.H. Bwhahaha... =(

    Quote
    Faulting application codeblocks.exe,
    version 13.12.0.0,

    faulting module wxmsw28u_gcc_cb.dll,
    version 2.8.12.0,

    fault address 0x00413d40.

    when I try to run it through the GDB... DING DING!! We have a winner!  ^_^ lol

    Quote
    Program received signal SIGSEGV, Segmentation fault.

    0x6cc8ded4 in
    wxmsw28u_gcc_cb!_ZNK13wxArrayString5IndexEPKwbb ()
    from C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll



    ps: if this deserves its own thread I or a mod can move  it there. =)


    EDIT:
    I tested out deleting all CodeBlocks project files including the layout file..
    then re-ran it through gdb still crashes like above

    Notepad2(v4.2.25)_src.rar
    here is the archive with the src for testing... (;p because I couldn't upload it here as an attachment =P)
    Includes Notepad 2's src, scintilla src, and the cmd-batch file I created for debugging (customize to your system layout)
    « Last Edit: December 31, 2014, 09:12:53 am by Melchior »
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 12006
      • Travis build status
    Re: The 06 December 2014 build (10050) is out.
    « Reply #2 on: December 31, 2014, 10:33:11 am »
    You need to rebuild codeblocks with symbols to get meaningful backtraces.
    (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!]

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #3 on: December 31, 2014, 11:53:20 am »
    I am not compiling it myself.... if you dev's feel like adding the debugging symbols to the next lightly build.. I will try again...

    otherwise I linked to a archive containing the notepad 2 src code and mentioned steps so some one else can test it too

    I updated txt file with back trace info I could get...

    .... considering this is a nightly why is it all being compiled with debugging symbols to begin with?!
    « Last Edit: December 31, 2014, 11:58:12 am by Melchior »
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 12006
      • Travis build status
    Re: The 06 December 2014 build (10050) is out.
    « Reply #4 on: December 31, 2014, 12:07:08 pm »
    .... considering this is a nightly why is it all being compiled with debugging symbols to begin with?!
    I don't see any symbols in the txt file. Everything has been stripped.
    (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!]

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #5 on: December 31, 2014, 03:35:17 pm »
    statement correction:
    .... considering that this is a nightly, why is it not  always being compiled with debugging symbols to begin with?!

    I what I am trying to say is considering that it is a nightly dev build why are there not already symbols built into it?



    while it is true the symbols have been stripped.... there are some clues maybe not enough but some....
    Quote
    (gdb) bt
    #0  0x6cc8ded4 in wxmsw28u_gcc_cb!_ZNK13wxArrayString5IndexEPKwbb () from C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll
    #1  0x618cf91e in codeblocks!_ZN11ProjectFile14AddBuildTargetERK8wxString () from C:\Dev-CodeBlocks\codeblocks.dll
    #2  0x7050a83d in ?? () from C:\Dev-CodeBlocks\share\codeblocks\plugins\projectsimporter.dll
    #3  0x7050a6a0 in ?? () from C:\Dev-CodeBlocks\share\codeblocks\plugins\projectsimporter.dll
    #4  0x70510591 in ?? () from C:\Dev-CodeBlocks\share\codeblocks\plugins\projectsimporter.dll
    #5  0x7051118d in ?? () from C:\Dev-CodeBlocks\share\codeblocks\plugins\projectsimporter.dll
    #6  0x70523205 in ?? () from C:\Dev-CodeBlocks\share\codeblocks\plugins\projectsimporter.dll
    #7  0x705244b5 in ?? () from C:\Dev-CodeBlocks\share\codeblocks\plugins\projectsimporter.dll
    #8  0x00483634 in ?? ()
    #9  0x00483b39 in ?? ()
    #10 0x004068a9 in ?? ()
    #11 0x004082e7 in ?? ()
    #12 0x6cc71e85 in wxmsw28u_gcc_cb!_Z14wxUninitializev () from C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll
    #13 0x6ccc9010 in wxmsw28u_gcc_cb!_Z7wxEntryP11HINSTANCE__S0_Pci () from C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll
    #14 0x004022a8 in ?? ()
    #15 0x004010fd in ?? ()
    #16 0x00000000 in ?? ()
    wxmsw28u_gcc_cb.dll
    codeblocks.dll
    projectsimporter.dll
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5179
    Re: The 06 December 2014 build (10050) is out.
    « Reply #6 on: January 01, 2015, 03:22:34 pm »
    the binaries of a nightly are indeed stripped, in order to keep the upload/dowload size acceptable.

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #7 on: January 01, 2015, 05:01:54 pm »
    understandable... but unless you plan to upload a debug version for me to test you guys will have to do it on your own...
    I gave the instructions to repeat and a copy of Notepad2's src code complete with the Codeblocks & VC project files
    plus the batch file I used to  test it.

    Debugging (gdb)_CodeBlocks opening Notepad2 vcproj file.cmd
    Code: [Select]
    @ECHO on
    gdb -readnow --args "C:\Dev-CodeBlocks\codeblocks.exe" Notepad2.vcproj
    pause
    shortened version.... as I copied and customized an older cmd to make it easier...


    oohh yah if you are using a newer version of Windows like 7+
    you can use a neat program called Types, comment on FileHippo is where I originally heard of it..

    http://izt.name/apps/types/
    http://izt.name/apps/types/new.rss  <<-- Suffices as a change-log. =D

    that and it requires .NET framework 2+
    it seems to be loading with .NET(v2), in the JIT debug-log I am getting on this latest crash I am testing on WinXP-64bit...
    overall its a good program and at last  ihad what I needed to make the best use of Windows 7,
    that is I could finally create ALL of the custom file type associations I use... ;^_^;
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #8 on: January 06, 2015, 11:24:10 am »
    IO got the repo downloaded  I love TortoiseSVN ^_^

    got wxWidgets downloaded now just figuring out where to put it....
    I had stored archives of wxWidgets v2.8.11 and v2.9.5 from years ago (2010 & 2013) can't recall ever using them.. I must have had something I intended to compile but got frustrated with it so let it go...

    so I have v2.8.12 &  v3.0.2 ^_^
    should I bother with v2.8 or just go for v3?!

    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Online BlueHazzard

    • Developer
    • Lives here!
    • *****
    • Posts: 2497
    Re: The 06 December 2014 build (10050) is out.
    « Reply #9 on: January 06, 2015, 11:44:05 am »
    use v2.8. v3 has still some annoying error messages and bugs. With v2.8 you are sure that all is working.

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #10 on: January 06, 2015, 11:59:35 am »
    use v2.8. v3 has still some annoying error messages and bugs. With v2.8 you are sure that all is working.
    Hi BlueHazzard, thx for the advice =D

    Question....

    Do I want

    wxMSW (v2.8.12)_src        (97MB)
    or
    wxWidgets (v2.8.12)_src   (122MB)

    I am going with the wxMSW one....
    and the setup.h HELL ;_;
    and that was trying to import the MS VS workspace (wx_dll.dsw).....
    so I am trying the cmd/makefile method now..


    Code: [Select]
    mingw32-make -f makefile.gcc BUILD=release UNICODE=1 MONOLITHIC=1 SHARED=1
    pause


    Code: [Select]
    mingw32-make -f makefile.gcc BUILD=debug UNICODE=1 MONOLITHIC=1 SHARED=1
    pause


    Code: [Select]
    mingw32-make -f makefile.gcc BUILD=debug   clean
    mingw32-make -f makefile.gcc BUILD=release clean
    pause


    I had to create the batch files myself... wxWidgets needs help   :'( :-\

    nope that didn't work either.... needed the "SHARED=1" as well duh?!


    whats worse than that  headache...

    is CodeBlocks src does not seem to have a debug target...

    aside from manually telling each project to to add "-g"..
    there is a target "all" just no debug target...   ;;;;___;;;;;

    so far I have "wxmsw28ud_gcc_custom.dll" built....

    though I made note that "wxmsw28u_gcc_cb.dll" is listed internally as said name...

    will there be any issues using this one, wxmsw28ud_gcc_custom.dll
    and do I have to rename it to wxmsw28u_gcc_cb.dll?
    « Last Edit: January 06, 2015, 03:46:08 pm by Melchior »
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #11 on: January 08, 2015, 11:46:28 am »
    So compiling done (yesterday).... after hours I had to manually add 'd' to the append 'ud' for the wx..
    and  I to manually set the -g flag in each and ever project file ;_;

    I compiled wx as 
    - wxmsw28ud_gcc_custom.dll
    mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=debug UNICODE=1

    so I could debug/report... but trying to run errors out with
    dll is debug but exe is not debug...

    and I modified the update.bat to comment out the strip commands...

    so what am I missing
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Online BlueHazzard

    • Developer
    • Lives here!
    • *****
    • Posts: 2497
    Re: The 06 December 2014 build (10050) is out.
    « Reply #12 on: January 08, 2015, 03:35:50 pm »
    So compiling done (yesterday).... after hours I had to manually add 'd' to the append 'ud' for the wx..
    and  I to manually set the -g flag in each and ever project file ;_;

    You could have used the global variable "cb_release_type" and add there "-g" in the "base"
    (Settings->Global Variable->Current Variable->cb_release_type->base = -g)

    so I could debug/report... but trying to run errors out with
    dll is debug but exe is not debug...

    try to fresh rebuild everything (i had the error also a lot times, but i don't remember what i have done  :-\ )

    and I modified the update.bat to comment out the strip commands...
    good idea  ;)

    You can also look at full build log and check if the right build where used...

    and that was trying to import the MS VS workspace (wx_dll.dsw).....
    never try this, if you are going with the gcc...
    better use the makefile way...

    will there be any issues using this one, wxmsw28ud_gcc_custom.dll
    and do I have to rename it to wxmsw28u_gcc_cb.dll?
    if the settings for wxWidgets are right, i never had to do anything like that...


    greetings

    Offline Melchior

    • Multiple posting newcomer
    • *
    • Posts: 63
    • Sage of Life, Reason, and Time
    Re: The 06 December 2014 build (10050) is out.
    « Reply #13 on: January 09, 2015, 02:24:42 am »
    You could have used the global variable "cb_release_type" and add there "-g" in the "base"
    (Settings->Global Variable->Current Variable->cb_release_type->base = -g)

    when you mean base you mean the user-defined-fields right?
    Quote
    User-defined Fields:
    txt-box1: [base = -g]

    or do you mean this:
    base="F:\Dev-src\CodeBlocks_src -g"





    ______________________________________________________
    Actually I copied the bat file then edited it.   loi  ;D

    on that note how about renaming all the .bat's to .cmd  ;D  .cmd looks so much better
    .bat is kinda like DOS era and such...

    I have attached a copy of the update_debug.bat can you guys please get it committed?
    :: Commented out to allow symbols to remain so debugging can be done.
    :: if more is needed for debugging to work correctly , Devs please edit as need.


    also, please add to the ignore list as they were not on it:

    plugins/contrib/FortranProject/FortranProject_cbsvn.depend
    plugins/contrib/FortranProject/FortranProject_cbsvn.layout


    I attached an archive containing 3 .cmd files
    makeWX_dll__Clean_ALL.cmd
    makeWX_dll__Debug.cmd
    makeWX_dll__Release.cmd

    which are setup to use the gcc make files ^_^
    « Last Edit: January 09, 2015, 02:29:49 am by Melchior »
    (PC Specs)
    CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
    Motherboard: Asus SABERTOOTH 990FX R2.0
    GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
    OS: Windows 7 Ultimate 64-bit SP1 (x64)

    Online ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5226
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 06 December 2014 build (10050) is out.
    « Reply #14 on: January 09, 2015, 04:50:54 am »
    @Melchior, normally C::B is built against release version of wx library, but you can build C::B against debug version of wx library, see:
    Developer documentation - CodeBlocks
    Quote
    You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: patch to build C::B against wx debug library

    About the "cb_release_type", this can be opened by click on the
    Menu->Settings->Global Variables
    And in the opened Global Variable Editor dialog, edit or add one variable named "cb_release_type", and set its  base filed(Under Built-in field panel) as "-g". (note no quotes).
    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.