Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on May 29, 2014, 12:29:42 am

Title: The 28 May 2014 build (9781) is out.
Post by: killerbot on May 29, 2014, 12:29:42 am
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 (http://forums.codeblocks.org/index.php/topic,3232.0.html).

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

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 28 May 2014 build (9781) is out.
Post by: nexon7 on May 30, 2014, 04:28:05 am
The easiest tutorial for installing codeblocks nightly and setting TDM GCC 32 and 64 bit (download from tdm-gcc site) is here   https://nexon7.wordpress.com/2013/09/03/how-to-install-codeblock-nightly-build-with-latest-gcc-compiler-32-bit-and-64-bit/  
This build 9781 works like charm :)
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nasty_wolverine on May 30, 2014, 11:20:30 am
Is there a documented bug about the astyle formatter? recently it has been going wack moving code all over the place, like from one function to another.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: stahta01 on May 30, 2014, 07:13:38 pm
Is there a documented bug about the astyle formatter? recently it has been going wack moving code all over the place, like from one function to another.

I have NOT noticed it; but, I have NOT been using CB SVN version 9781.
I suggest posting the normal info and how to duplicate the issue.
OS Name and version; wxWidgets version; source of Code::Blocks (self built or ?).

Tim S.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nasty_wolverine on May 30, 2014, 08:50:41 pm
before:
Code
#include "hash_manager.h"

int ChashManager::calculate_hash(float x, float y)
{
if( ((x >= 4.0f)||(x < 0.0f)) || ((y >= 4.0f)||(y < 0.0f)) )
{
return 0xFFFF;
}
else
{
return ( ((int)y*4) + (int)x); //TO DO: how do i control hash size???
}
}

int ChashManager::getbin(vector2f position, vector2f offset, vector2f corner, vector2f camera)
{
    vector2f temp;

temp = position + offset + corner;
temp = temp - camera; //collapse to camera space

return calculate_hash(temp.x, temp.y);
}

void ChashManager::flush()
{
hashbucket_.clear();
objectindex_.clear();
}

void ChashManager::add(int id, Chitbox phitbox, vector2f position, vector2f camera)
{
//main loop for every available hitbox in hitbox collection
for(std::vector<circle2f>::size_type i = 0; i < phitbox.collection.size(); i++)
{
    //phitbox.collection[i].r
    Sbox box();






}
}

void addtomap(int id, Sbox box)
{
    if( box.box_min == 0xffff && box.box_max == 0xffff && box.box_lt == 0xffff && box.box_rb == 0xffff )
{
return; // out of scene
}

    int ymod = 0;

int xspread = box.box_rb - box.box_min;
int yspread = (box.box_max - box.box_rb)/4;

for(int y = 0; y <= yspread; y++)
{
for(int x = box.box_min; x <= (xspread + box.box_min); x++)
{
//p_ent->hitbox.binlist.push_back(ymod + x);//bin number here is (ymod+x)
}
ymod += 4;
}
}

void delimit_box(Sbox &box)
{
    //lt, max
//min, rb

if( box.box_min == 0xffff && box.box_max == 0xffff && box.box_lt == 0xffff && box.box_rb == 0xffff )
{
return; // out of scene
}

//first scenario - min is Oxffff (object in lower left corner)
if((box.box_min == 0xffff) && (box.box_max != 0xffff))
{
if( box.box_lt == 0xffff && box.box_rb == 0xffff )
{
box.box_rb = box.box_max%4;
box.box_lt = 4*(box.box_max/4);
box.box_min = 0;
}
else if( box.box_lt != 0xffff && box.box_rb == 0xffff )
{
box.box_min = box.box_lt%4;
box.box_rb = box.box_max%4;
}
else if( box.box_lt == 0xffff && box.box_rb != 0xffff )
{
box.box_lt = 4*(box.box_max/4);
box.box_min = 4*(box.box_rb/4);
}
}
//second scenario- max is 0xffff (object in upper right corner)
else if ( (box.box_min != 0xffff) && (box.box_max == 0xffff) )
{
if( box.box_lt == 0xffff && box.box_rb == 0xffff )
{
box.box_max = 15;
box.box_lt = (box.box_min%4)+12;
box.box_rb = (((box.box_min/4)+1)*4)-1;
}
else if( box.box_lt != 0xffff && box.box_rb == 0xffff )
{
box.box_max = (((box.box_lt/4)+1)*4)-1;
box.box_rb = (((box.box_min/4)+1)*4)-1;
}
else if( box.box_lt == 0xffff && box.box_rb != 0xffff )
{
box.box_max = 12+(box.box_rb%4);
box.box_lt = 12+(box.box_min%4);
}
}
//second scenario- max and min is 0xffff (object in upper right/lower left corner)
else if ( (box.box_min == 0xffff) && (box.box_max == 0xffff) )
{
if(box.box_rb == 0xffff)
{
box.box_max = (((box.box_lt/4)+1)*4)-1;
box.box_min = box.box_lt%4;
box.box_rb = 3;
}
else
{
box.box_lt = 12;
box.box_max = 12+(box.box_rb%4);
box.box_min = 4*(box.box_rb/4);
}
}
}

std::vector<int> ChashManager::getBinElements(int pid)
{


}



after:
Code
#include "hash_manager.h"

int ChashManager::calculate_hash(float x, float y)
{
if( ((x >= 4.0f)||(x < 0.0f)) || ((y >= 4.0f)||(y < 0.0f)) )
{
return 0xFFFF;
}
else
{
return ( ((int)y*4) + (int)x); //TO DO: how do i control hash size???
}
}

int ChashManager::getbin(vector2f position, vector2f offset, vector2f corner, vector2f camera)
{
vector2f temp;

temp = position + offset + corner;
temp = temp - camera; //collapse to camera space
temp = temp - camera; //collapse to camera space
return calculate_hash(temp.x, temp.y);
}

void ChashManager::flush()
{
hashbucket_.clear();
objectindex_.clear();
}

void ChashManager::add(int id, Chitbox phitbox, vector2f position, vector2f camera)
{
//main loop for every available hitbox in hitbox collection
for(std::vector<circle2f>::size_type i = 0; i < phitbox.collection.size(); i++)
{
//phitbox.collection[i].r
Sbox box();






}
}

void addtomap(int id, Sbox box)
{
if( box.box_min == 0xffff && box.box_max == 0xffff && box.box_lt == 0xffff && box.box_rb == 0xffff )
{
return; // out of scene
}
{
int ymod = 0;

int xspread = box.box_rb - box.box_min;
int yspread = (box.box_max - box.box_rb)/4;

for(int y = 0; y <= yspread; y++)
{
for(int x = box.box_min; x <= (xspread + box.box_min); x++)
{
//p_ent->hitbox.binlist.push_back(ymod + x);//bin number here is (ymod+x)
}
ymod += 4;
}
}

void delimit_box(Sbox &box)
{
//lt, max
//min, rb
int yspread = (box.box_max - box.box_rb)/4;
if( box.box_min == 0xffff && box.box_max == 0xffff && box.box_lt == 0xffff && box.box_rb == 0xffff )
{
return; // out of scene
}
for(int y = 0; y <= yspread; y++)
//first scenario - min is Oxffff (object in lower left corner)
if((box.box_min == 0xffff) && (box.box_max != 0xffff))
{
if( box.box_lt == 0xffff && box.box_rb == 0xffff )
{
box.box_rb = box.box_max%4;
box.box_lt = 4*(box.box_max/4);
box.box_min = 0;
}
else if( box.box_lt != 0xffff && box.box_rb == 0xffff )
{
box.box_min = box.box_lt%4;
box.box_rb = box.box_max%4;
}
else if( box.box_lt == 0xffff && box.box_rb != 0xffff )
{
box.box_lt = 4*(box.box_max/4);
box.box_min = 4*(box.box_rb/4);
}
}
//second scenario- max is 0xffff (object in upper right corner)
else if ( (box.box_min != 0xffff) && (box.box_max == 0xffff) )
{
if( box.box_lt == 0xffff && box.box_rb == 0xffff )
{
box.box_max = 15;
box.box_lt = (box.box_min%4)+12;
box.box_rb = (((box.box_min/4)+1)*4)-1;
}
else if( box.box_lt != 0xffff && box.box_rb == 0xffff )
{
box.box_max = (((box.box_lt/4)+1)*4)-1;
box.box_rb = (((box.box_min/4)+1)*4)-1;
}
else if( box.box_lt == 0xffff && box.box_rb != 0xffff )
{
box.box_max = 12+(box.box_rb%4);
box.box_lt = 12+(box.box_min%4);
}
}
//second scenario- max and min is 0xffff (object in upper right/lower left corner)
else if ( (box.box_min == 0xffff) && (box.box_max == 0xffff) )
{
if(box.box_rb == 0xffff)
{
box.box_max = (((box.box_lt/4)+1)*4)-1;
box.box_min = box.box_lt%4;
box.box_rb = 3;
}
else
{
box.box_lt = 12;
box.box_max = 12+(box.box_rb%4);
box.box_min = 4*(box.box_rb/4);
}
}
}
for(int x = box.box_min; x <= (xspread + box.box_min); x++)
std::vector<int> ChashManager::getBinElements(int pid)
{
//p_ent->hitbox.binlist.push_back(ymod + x);//bin number here is (ymod+x)
}
}



as you can see, astyle formatting things is out of whack for me, there is some code duplication going on in the getbin method, and right near the end its copying code from somewhere else.

this is using nightly 9781 in windows 7 64bit
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on May 30, 2014, 09:01:57 pm
as you can see, astyle formatting things is out of whack for me, there is some code duplication going on in the getbin method, and right near the end its copying code from somewhere else.

this is using nightly 9781 in windows 7 64bit
Can you please describe the exact steps to reproduce (including the astyle settings you use).
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nasty_wolverine on May 30, 2014, 09:16:32 pm
Can you please describe the exact steps to reproduce (including the astyle settings you use).
well on the settings side, i use gnu indentation, its set on use tabs instead of spaces, indentation size is 4. everything else is unchecked. on how to reproduce it, the code I pasted before is in a file called hash_manager.cpp, i activate the file in the editor, go to plugins and click on source code formatter, and that happens. also, i checked with a few different styles of formatting, it does garble things up, but in different ways.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Alpha on May 31, 2014, 04:32:40 am
Note, most likely rev 9575 (http://cb.biplab.in/websvn/revision.php?rev=9575) is the cause; I do not have time to look into it right now, so consider reverting if it is not an easy fix.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nasty_wolverine on May 31, 2014, 11:25:32 am
Note, most likely rev 9575 (http://cb.biplab.in/websvn/revision.php?rev=9575) is the cause; I do not have time to look into it right now, so consider reverting if it is not an easy fix.
Its not something that i cant live without, indentation while typing code works fine. and i can always manually align code.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 08, 2014, 06:04:34 pm
Is there a problem with auto-completion?

I am using svn9793 on debian testing (64-bit) and as soon as I complete <stdio it stops drop down listbox and I have to press Ctrl-space to auto-complete it.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nanyu on June 08, 2014, 09:32:38 pm
url link doesn't work :
click    http://prdownload.berlios.de/codeblocks/CB_20140528_rev9781_win32.7z
will open the web "http://www.berlios.de/"  homepage only。


--
firefox 29.01 / IE 11
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ollydbg on June 09, 2014, 02:23:58 am
url link doesn't work :
click    http://prdownload.berlios.de/codeblocks/CB_20140528_rev9781_win32.7z
will open the web "http://www.berlios.de/"  homepage only。


--
firefox 29.01 / IE 11
It looks like the whole https://developer.berlios.de/projects/codeblocks/ was down. They have said before, see: berlios will close project host in 2014.04 (http://forums.codeblocks.org/index.php/topic,18874.0.html)


EDIT
You can download the bin files from mirror sites: http://sourceforge.net/projects/codeblocks.berlios/files/
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 09, 2014, 02:39:30 pm
Is there a problem with auto-completion?

I am using svn9793 on debian testing (64-bit) and as soon as I complete <stdio it stops drop down listbox and I have to press Ctrl-space to auto-complete it.
Another thing I have noticed is that under a C project if you use C99 syntax for structures and press "dot" to get a member, instead of getting the name of a desired member, you only get C++ keywords.

Is it possible for the parser to search only for C data members, reserved keywords, and such?

Thank you.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ollydbg on June 09, 2014, 03:36:34 pm
Is there a problem with auto-completion?

I am using svn9793 on debian testing (64-bit) and as soon as I complete <stdio it stops drop down listbox and I have to press Ctrl-space to auto-complete it.
Another thing I have noticed is that under a C project if you use C99 syntax for structures and press "dot" to get a member, instead of getting the name of a desired member, you only get C++ keywords.

Is it possible for the parser to search only for C data members, reserved keywords, and such?

Thank you.
You mean:
http://www.dribin.org/dave/blog/archives/2010/05/15/c99_syntax/
Code
NSPoint point = { .x = 0, .y = 0};
?

1, we should know it is an initialization statement.
2, we are after the dot.
3, we are in a C file, but we have C99 option enabled.

The hardest part is 1. How do we locate that we are in an C stile initialization? Currently, CC only remember the "{}" pair for function bodies and class definition.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 09, 2014, 04:13:15 pm
You mean:
http://www.dribin.org/dave/blog/archives/2010/05/15/c99_syntax/
Code
NSPoint point = { .x = 0, .y = 0};
?
Yes, exactly.

1, we should know it is an initialization statement.
2, we are after the dot.
3, we are in a C file, but we have C99 option enabled.

The hardest part is 1. How do we locate that we are in an C stile initialization? Currently, CC only remember the "{}" pair for function bodies and class definition.
As far as I know, GCC currently has C99/C11 features added (enabled?) in C by default and currently waiting to incorporate C11 as their default flag.

Should not it work since point #3 is partially available by default?
Title: Re: The 28 May 2014 build (9781) is out.
Post by: stahta01 on June 09, 2014, 04:22:25 pm
You mean:
http://www.dribin.org/dave/blog/archives/2010/05/15/c99_syntax/
Code
NSPoint point = { .x = 0, .y = 0};
?
Yes, exactly.

1, we should know it is an initialization statement.
2, we are after the dot.
3, we are in a C file, but we have C99 option enabled.

The hardest part is 1. How do we locate that we are in an C stile initialization? Currently, CC only remember the "{}" pair for function bodies and class definition.
As far as I know, GCC currently has C99/C11 features added (enabled?) in C by default and currently waiting to incorporate C11 as their default flag.

Should not it work since point #3 is partially available by default?

Feel free to submit a patch for CB's CC (Code Completion) if you think it is so easy to do.

Tim S.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 09, 2014, 04:51:24 pm
Feel free to submit a patch for CB's CC (Code Completion) if you think it is so easy to do.

Tim S.

I can't see anywhere I mention such thing; I just asked. there's no need to be sarcastic.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ollydbg on June 10, 2014, 01:59:29 am
Feel free to submit a patch for CB's CC (Code Completion) if you think it is so easy to do.
Tim S.
I can't see anywhere I mention such thing; I just asked. there's no need to be sarcastic.
Hi, ToApolytoXaos, I don't understand this sentence.
Quote
Should not it work since point #3 is partially available by default?
, can you explain more?

Our CodeCompletion plugin has its own parser, the parser does not have the scale as a normal compiler's parser (parser in gcc or clang). I think it was not quite easy to add the feature you request, it is doable, but the developers(include me) are focus to fix other parts of CC which I think is more important. So, we welcome any contribute to CC.  :)



Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 10, 2014, 02:53:02 pm
I was referring at the "if you think it is so easy to do" part. I did not ask for anything; all I needed was more info, academically-wise you could say, that's all.

As far as I know certain features like for example // single line comments are permitted as also the aforementioned structure example. I did not use any flags and was able to compile just fine.

What puzzled me was the suggestion list that would include only C++ keywords and not a single C word at all; that's why I have asked for more information. I did not come here to play the wise guy or to start an unnecessary argument.

Sometimes a literal translation from one language to another can lead to such misinterpretations and most of the time instead of investing time and efford to resolve issues and bugs, let alone share ideas, we waste it to argue who said what and why having as a result to kill the educating (sharing) spirit in favor of ego.

That's just sad I would say...a lot!
Title: Re: The 28 May 2014 build (9781) is out.
Post by: stahta01 on June 10, 2014, 03:11:32 pm
What puzzled me was the suggestion list that would include only C++ keywords and not a single C word at all; that's why I have asked for more information. I did not come here to play the wise guy or to start an unnecessary argument.

You came here to waste bandwidth on topics not valid in this sub forum!

If you wish to discuss or suggest new feature this thread and sub-forum is NOT the correct place!

This thread is for new bugs in this nighty build. And, other questions and info related to this nighty build.

It is NOT a general thread about using CB or request of new features!

Tim S. 
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 10, 2014, 04:52:48 pm
I understand.

You could say this from the start in a good way by the way; no need to sound harsh or aggressive.

No wonder why people are scared to ask questions in here.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nanyu on June 13, 2014, 04:01:55 pm
url link doesn't work :
click    http://prdownload.berlios.de/codeblocks/CB_20140528_rev9781_win32.7z
will open the web "http://www.berlios.de/"  homepage only。


--
firefox 29.01 / IE 11
It looks like the whole https://developer.berlios.de/projects/codeblocks/ was down. They have said before, see: berlios will close project host in 2014.04 (http://forums.codeblocks.org/index.php/topic,18874.0.html)


EDIT
You can download the bin files from mirror sites: http://sourceforge.net/projects/codeblocks.berlios/files/


Thanks!
But why we still use a old url link in this page?
Title: Re: The 28 May 2014 build (9781) is out.
Post by: q4a on June 14, 2014, 06:42:15 pm
Hi all.

I'm using Lubuntu (LXDE on Ubuntu) 14.04 amd64 fresh installed. I have installed C::B 13.12 from Ubuntu official repo, but it crashed few times and I decided to test Nightly builds.
I tested rev 9781 from PPA for pasgui (https://launchpad.net/~pasgui/+archive/ppa/) and rev 9791 from Jens repo (http://apt.jenslody.de/) - both has problem with Ctrl-C and Ctrl-V.
Copy and Paste works from toolbar and I can undo changes with Ctrl-Z, but Copy and Paste with Ctrl-C and Ctrl-V does not work.

Should I create ticket to SF or it's known problem or it's problem with my system?
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Aleksandr on June 14, 2014, 08:29:23 pm
Since there was no answer, I will ask here because I use this nightly build. Can it be considered a bug, the behavior of the program described in this topic?
http://forums.codeblocks.org/index.php/topic,19256.0.html (http://forums.codeblocks.org/index.php/topic,19256.0.html)
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 17, 2014, 02:02:05 am
Please don't cross-post!
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 20, 2014, 06:57:18 pm
svn9817 compiled with GCC 4.9.0 on Debian testing (64-bit) had just crashed while typing a macro in C.

I presume it has something to do with the parser, because it would not let me include any structure member while pressing dot or Ctrl-Space. I have reparsed it and still nothing.

Code
<?xml version="1.0" encoding="utf-8"?>
<report version="1.0" kind="exception">
  <system description="Linux 3.14-1-amd64 x86_64"/>
   ...
   ... [ deleted unnecessary modules to save space ]
   ...
  <stack>
    <frame level="0"/>
    <frame level="1" function="wxsResourceTree::InvalidateItemData(wxsResourceTreeItemData*)" offset="00000010"/>
    <frame level="2" function="wxsResourceTreeItemData::~wxsResourceTreeItemData()" offset="00000036"/>
    <frame level="3"/>
    <frame level="4"/>
    <frame level="5" function="wxGenericTreeItem::~wxGenericTreeItem()" offset="00000016"/>
    <frame level="6" function="wxGenericTreeItem::DeleteChildren(wxGenericTreeCtrl*)" offset="0000002d"/>
    <frame level="7" function="wxGenericTreeCtrl::Delete(wxTreeItemId const&amp;)" offset="00000106"/>
    <frame level="8" function="wxGenericTreeCtrl::DeleteAllItems()" offset="00000023"/>
    <frame level="9" function="wxGenericTreeCtrl::~wxGenericTreeCtrl()" offset="00000050"/>
    <frame level="10" function="wxTreeCtrl::~wxTreeCtrl()" offset="00000043"/>
    <frame level="11" function="wxsResourceTree::~wxsResourceTree()" offset="00000061"/>
    <frame level="12" function="wxsResourceTree::~wxsResourceTree()" offset="00000018"/>
    <frame level="13" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
    <frame level="14" function="wxWindow::~wxWindow()" offset="00000062"/>
    <frame level="15" function="wxPanel::~wxPanel()" offset="00000009"/>
    <frame level="16" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
    <frame level="17" function="wxWindow::~wxWindow()" offset="00000062"/>
    <frame level="18" function="wxSplitterWindow::~wxSplitterWindow()" offset="00000009"/>
    <frame level="19" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
    <frame level="20" function="wxWindow::~wxWindow()" offset="00000062"/>
    <frame level="21" function="wxsStoringSplitterWindow::~wxsStoringSplitterWindow()" offset="0000002a"/>
    <frame level="22" function="wxsStoringSplitterWindow::~wxsStoringSplitterWindow()" offset="00000018"/>
    <frame level="23" function="wxWindowBase::Destroy()" offset="0000000f"/>
    <frame level="24" function="wxAuiNotebook::DeletePage(unsigned long)" offset="000000b4"/>
    <frame level="25" function="wxAuiNotebook::~wxAuiNotebook()" offset="00000032"/>
    <frame level="26" function="cbAuiNotebook::~cbAuiNotebook()" offset="00000053"/>
    <frame level="27" function="cbAuiNotebook::~cbAuiNotebook()" offset="00000018"/>
    <frame level="28" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
    <frame level="29" function="wxWindow::~wxWindow()" offset="00000062"/>
    <frame level="30" function="MainFrame::~MainFrame()" offset="00000000" file="/home/stefanos/svn_code/CodeBlocks/src/src/main.cpp" line="660"/>
    <frame level="31" function="MainFrame::~MainFrame()" offset="00000000" file="/home/stefanos/svn_code/CodeBlocks/src/src/main.cpp" line="660"/>
    <frame level="32" function="wxAppBase::CleanUp()" offset="00000036"/>
    <frame level="33" function="wxEntryCleanup()" offset="00000050"/>
  </stack>
</report>
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 20, 2014, 08:50:51 pm
Seems like a wxsmith related crash...
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nasty_wolverine on June 20, 2014, 09:10:03 pm
Note, most likely rev 9575 (http://cb.biplab.in/websvn/revision.php?rev=9575) is the cause; I do not have time to look into it right now, so consider reverting if it is not an easy fix.

Regarding the autoformat/indent not working properly, i think i figured out whats making that happen. its the return characters(^M). when i was editing the same files with vim/emacs, i noticed that most of the places where autoformat was screwing up was where the return characters were (the code was carried over from a previous visual studio project). So i guess autoformat cant handle ^M and that throws it off.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 20, 2014, 10:22:20 pm
Seems like a wxsmith related crash...
That's weird; I'm not using wxSmith at all. It's a plain C console application, made long time ago with "Empty Project".
Title: Re: The 28 May 2014 build (9781) is out.
Post by: nasty_wolverine on June 21, 2014, 01:35:51 am
Note, most likely rev 9575 (http://cb.biplab.in/websvn/revision.php?rev=9575) is the cause; I do not have time to look into it right now, so consider reverting if it is not an easy fix.

Regarding the autoformat/indent not working properly, i think i figured out whats making that happen. its the return characters(^M). when i was editing the same files with vim/emacs, i noticed that most of the places where autoformat was screwing up was where the return characters were (the code was carried over from a previous visual studio project). So i guess autoformat cant handle ^M and that throws it off.

sorry, apparently not. still happens after i have removed those symbols.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 10:19:05 am
About crashing issue: Can anyone with svn9817 try to create a macro like

Code
#define arrsize(array) (sizeof(array) / sizeof(array[0]) )

and let me know if it crashes on insertion of the first parenthesis (?

UPDATE: I ran it with GDB and got the following line upon repeating the aforementioned procedure:

Code
0x00007fffe553605e in wxsResourceTree::InvalidateItemData (this=0x0, ItemData=0x49b6b50) at wxsresourcetree.cpp:212
212         if ( m_Data == ItemData )
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 21, 2014, 12:36:56 pm
Are you sure you build is fine?
If you search the source you'll see that wxsResourceTree is part of wxSmith.
Can you try to unload it and try to reproduce the issue again?

Have you thought about learning how to make dep packages? I doubt it is that hard, but I'm sure it produces reliable binaries.
Using ./configure && make && make install && make unininstall is quite error prone.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 12:53:23 pm
Are you sure you build is fine?
Well, it built just fine without reporting any further issue, but seriously I don't know if it's "fine".

If you search the source you'll see that wxsResourceTree is part of wxSmith.
Can you try to unload it and try to reproduce the issue again?
Sure, I will do it right now and I will let you know.

Have you thought about learning how to make dep packages? I doubt it is that hard, but I'm sure it produces reliable binaries.
To be honest, it passed through my mind, but I did not give it a try; maybe it's a good time now, why not?

Using ./configure && make && make install && make unininstall is quite error prone.
To say such thing it means you know more than me and for sure you have far more traumatic experience than I.

I will try your suggestions and I will let you know.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on June 21, 2014, 01:56:15 pm
Using ./configure && make && make install && make unininstall is quite error prone.
To say such thing it means you know more than me and for sure you have far more traumatic experience than I.
If you build from a build-folder in (or outside) the C::B source-tree and install to a local folder below your home-directory you do not need "make uninstall" (which can fail miserably if file-paths have changed in makefiles).
You can always completely wipe-out your local build and install-folder and be sure no artefacts of former builds are left.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on June 21, 2014, 01:57:16 pm
Using ./configure && make && make install && make unininstall is quite error prone.
To say such thing it means you know more than me and for sure you have far more traumatic experience than I.
If you build from a build-folder in (or outside) the C::B source-tree and install to a local folder below your home-directory you do not need "make uninstall" (which can fail miserably if file-paths have changed in makefiles).
You can always completely wipe-out your local build and install-folder and be sure no artefacts of former builds are left.
But creating deb-files do not need anything but running dpkg-buildpackage from C::B's root-folder (the one containing the debian-folder).
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 02:27:03 pm
Yeah jens, I know. I have created the packages and the issue remains the same. I am repeating the steps as I am typing this message to make sure it's not my fault.

UPDATE: Yep, the issue remains the same. Can someone update to latest HEAD revision, compile it, and try a #define something() macro to see whether it crashes on first parenthesis or not?
UPDATE #2: Now that I have compiled .deb packages myself and managed to reproduce the crash, gdb reports the following:

Code
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff58c0880 in wxMutex::Lock() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 21, 2014, 02:56:16 pm
As Jens said using "make uninstall" requires great discipline and care, so it is not recommended in the long run.

Deb packages will fail to if you've not completely cleaned you system from old files!
So you have to uninstall all codeblocks related packages. Then search your folders and remove everything related to C::B, then install the packages.

I've tried your example in r9818 and it worked fine.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 21, 2014, 03:00:04 pm
This bt looks more plausible. Can you try to bisect the issue. r9808 seems like a first test revision.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 03:30:35 pm
Actually the first test revision I think and I might be wrong here is svn9802, based on log file.

By the way, I rolled back to svn9800, but dpkg-buildpackage -us -uc would generate files based on latest HEAD and not as required revision.

Can you please advice on this?
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ollydbg on June 21, 2014, 03:50:54 pm
Actually the first test revision I think and I might be wrong here is svn9802, based on log file.
Commit log of 9802:
Quote
* CC: apply Huki's patch, it is a small bug fix in nativeparser.cpp, NativeParser::ParseLocalBlock(). The function ParseLocalBlock() is only supposed to be run for function blocks(bodies), but it's actually run for any kind of code block (classes, etc). So for example if the user clicks on a class declaration, the entire class block will be parsed as if it's a local block and several token info (such as the line index) will be overwritten. To fix it a check is added. See: http://forums.codeblocks.org/index.php/topic,18315.msg132338.html#msg132338

-------------------------------
M(T ) : /trunk/src/plugins/codecompletion/nativeparser.cpp

...
UPDATE: Yep, the issue remains the same. Can someone update to latest HEAD revision, compile it, and try a #define something() macro to see whether it crashes on first parenthesis or not?
No crash here I only build C::B HEAD (rev 9818)with all the core plugins under WinXP.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on June 21, 2014, 03:57:06 pm
Actually the first test revision I think and I might be wrong here is svn9802, based on log file.

By the way, I rolled back to svn9800, but dpkg-buildpackage -us -uc would generate files based on latest HEAD and not as required revision.

Can you please advice on this?
The revision number used is the one in debian/changelog. It might not be the correct number.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 04:00:54 pm
Indeed it still points on the latest HEAD even though I ran ./boostrap right after reversing on r9800.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on June 21, 2014, 04:23:10 pm
Indeed it still points on the latest HEAD even though I ran ./boostrap right after reversing on r9800.
Make sure it is also reverted and remove the hidden file ".last_revision".
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 04:27:23 pm
Make sure it is also reverted and remove the hidden file ".last_revision".
Done so; still the same :/ It insists to do the same thing as before:

dpkg-buildpackage: source version 13.12svn9818
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on June 21, 2014, 04:37:19 pm
Do you have a tar.gz or similar source-ball on your hdd (from former run of dpkg-buildpackage) ?

By the way, I can confirm the crash on FC21 64-bit build with gcc4.9 !
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 04:40:55 pm
No, this is the first time I've tried creating debian packages.

Question: I read codecompletion.cpp file and can see many pointers in it not being released (cleared, null-ed should I say?) after their function member use.

Is there any smart pointer mechanism anywhere? For example, if you go to line 844 you see the pointer get initialized with whatever ed->GetColourSet(); is returning, but you don't see anywhere where this pointer gets null-ed or released.

I hope I haven't forgot the little C++ I knew all this time! lol
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 21, 2014, 05:14:07 pm
The object returned by GetColourSet it owned by the editor, so the callers don't have to delete it.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 21, 2014, 06:41:39 pm
I have found the problem. I have disabled every plugin and checked them one by one.

The problematic plugin is "SmartIndentCpp". It would crash the application upon parenthesis insertion.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on June 21, 2014, 11:45:19 pm
Can you reproduce this issue in a simle console project?
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 22, 2014, 12:01:06 am
As I have originally posted, the reproduction happened in an "Empty Project" that produces console output.

Jens reproduced the same on Fedora21 with GCC 4.9.0 64-bit.

By the way, I can confirm the crash on FC21 64-bit build with gcc4.9 !
Title: Re: The 28 May 2014 build (9781) is out.
Post by: Jenna on June 22, 2014, 11:19:49 am
I don't know why this happens, but the crash disappears if SmartIndent handles bracecompletion inside preprocessor-style also.
Debugging does not work correctly (for whatever reason, e.g. no backtrace).
No time to dig into it deeper at the moment.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 22, 2014, 12:37:23 pm
I have been struggling with the code since last night to decipher some parts of it, but I have failed miserably lol.

The only thing that caught my attention is the use of regular expressions. That's the place where you should pay attention IMHO.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: MortenMacFly on June 22, 2014, 03:10:31 pm
About crashing issue: Can anyone with svn9817 try to create a macro like
Code
#define arrsize(array) (sizeof(array) / sizeof(array[0]) )
Thats a bug in scintilla:
http://sourceforge.net/p/scintilla/bugs/1614

Will be fixed soon in C::B...
Title: Re: The 28 May 2014 build (9781) is out.
Post by: ToApolytoXaos on June 22, 2014, 03:20:53 pm
That's good to know. For the moment, I have the affected plugin disabled and works just fine.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: cacb on June 28, 2014, 01:20:55 am
Hi I would like to download this Nightly ready built for Windows, but the links in the main post don't work as you probably are aware. Where can I download the prebuilt nightly for Windows? Could the links perhaps be updated?

Ok, found mirror site http://sourceforge.net/projects/codeblocks.berlios/files/

Still suggest updating the main post.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: killerbot on June 29, 2014, 04:49:20 pm
a new nightly will be made this week
Title: Re: The 28 May 2014 build (9781) is out.
Post by: MortenMacFly on June 29, 2014, 07:59:16 pm
a new nightly will be made this week
I just realised that with BerliOS being gone we also lost the nightly archive except the mentioned BerliOS mirror. We should "copy" all nightlies from this to our official file data base at SF.NET... :P

Dev-volunteers with a fast internet connection wrt to uploads, please?! :-)

Edit: I've just created a folder at:
https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/

Edit2:
Copying... but unfortunately it looks like we have lost AT LEAST all nightlies form 2013... why the hell it is like that - I don't know.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: xawari on July 01, 2014, 11:06:51 am
If you need some previous nightlies archive or temporary www-hosting, I can help.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: White-Tiger on July 01, 2014, 03:55:10 pm
Well... it's not directly related to this nightly, but I hope you might be able to help anyway.

I've found out that the autosave plugin doesn't work for me when setup to use logrotate style...

Every time Code::Blocks crashes (and it happens from time to time) I loose my projects layout file.. (well it's there, have to use the *.layout.save file by manually renaming it)
Cause seem to be that wxWidgets cannot copy files to a file ending in ".temp" ... so changing autosave.cpp:143 from ".temp" to ".tmp" fixes it for me...
The behavior of wxWidgets looks weird to me though... why does the extension matter? And why can't it create files ending in ".temp" ?
Even though the wxCopyFile call at line 145 succeeds... Still never creates the file.
Title: Re:
Post by: MortenMacFly on July 01, 2014, 10:14:49 pm
Wer have an archive at sourceforge now, just the actual nightlies are gone.if you have backups of these, tell me where....that would be great.
Title: Re:
Post by: stahta01 on July 02, 2014, 12:53:52 am
Wer have an archive at sourceforge now, just the actual nightlies are gone.if you have backups of these, tell me where....that would be great.

I uploaded the two I found on my hard drive to here https://github.com/stahta01/cb_misc/tree/master/CB_NB (https://github.com/stahta01/cb_misc/tree/master/CB_NB)

Tim S.
Title: Re: The 28 May 2014 build (9781) is out.
Post by: teto on July 08, 2014, 02:34:54 pm
with this build (Ubuntu svn 9781) , if I allow more than one instance in the environement settings, my setting looks saved (If I reload CB, the box "Allow only one instance" is unchecked) but still, if I try to launch a 2nd instance, I got a popup "only one instance allowed".

Was this fixed in any newer nightly ?

regards
Title: Re: The 28 May 2014 build (9781) is out.
Post by: teto on July 09, 2014, 11:42:34 am
I also noticed that concerning syntax highlighting, my preference for "Active Line" color is reseted at every restart.
Title: Re:
Post by: MortenMacFly on July 09, 2014, 03:37:09 pm
I uploaded the two I found on my hard drive to here https://github.com/stahta01/cb_misc/tree/master/CB_NB (https://github.com/stahta01/cb_misc/tree/master/CB_NB)
Forgotten to tell: These have been transferred to SF.net. Thank you!
Title: Re: The 28 May 2014 build (9781) is out.
Post by: oBFusCATed on July 09, 2014, 09:09:08 pm
teto: I suppose C::B is crashing and no settings are save. Can you run C::B from console and see if it is printing something strange?
Title: Re: The 28 May 2014 build (9781) is out.
Post by: teto on July 16, 2014, 07:47:00 pm
oBFusCATed: can't reproduce :s but if it does I will do as you told me.