Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on July 06, 2014, 07:19:24 pm

Title: The 06 July 2014 build (9844) is out.
Post by: killerbot on July 06, 2014, 07:19:24 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 (http://forums.codeblocks.org/index.php/topic,3232.0.html).

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 July 2014 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2014/CB_20140706_rev9844_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 06 July 2014 build (9844) is out.
Post by: jens on July 06, 2014, 11:58:00 pm
As usual (and most of the time updated more frequently):

Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo (http://apt.jenslody.de/).
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 (http://rpm.jenslody.de) .
Title: Re: The 06 July 2014 build (9844) is out.
Post by: shurick on July 07, 2014, 06:12:12 pm
Packages for openSUSE (http://codeblocks.esy.es) (binaries and sources) for 32-bit and 64-bit.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: damorin on July 09, 2014, 08:16:40 pm
Hi,

C::B died unexpectedly while trying to open a file from the projects window. See attached RPT.

svn 9844
Windows XP SP3.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: oBFusCATed on July 09, 2014, 09:07:18 pm
damorin: Do you use the codesnippets plugin? Can you reproduce the crash more than once?
Title: Re: The 06 July 2014 build (9844) is out.
Post by: damorin on July 09, 2014, 10:07:26 pm
damorin: Do you use the codesnippets plugin? Can you reproduce the crash more than once?
Hi,

Nope and it occurred only once only a few hours after I installed it.


Title: Re: The 06 July 2014 build (9844) is out.
Post by: White-Tiger on July 23, 2014, 01:14:39 pm
well... got an issue with code completion closing a sec after opening... this exists in all versions of Code::Blocks IIRC...
Basically you write somethings that can be auto completed. such as "unsigned" (auto completion might drop in after "uns") this will open the typical code completion popup but it will also close within' 1 second if your mouse hovers any type of identifier.. because it opens that definition after 1 second.

This happens because with every character you write, the definition popup triggers... Normally it wouldn't trigger when you press CTRL-SPACE to open code completion... or pressing ENTF
So I guess you'll have to remove that from the definition popup.. or handle the case that code completion is open.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: White-Tiger on July 25, 2014, 02:14:49 am
Code completion parsing bug:
following code got missing functions in struct dafuq_t:
Code: [Select]
#define DLL_CALLCONV_ __stdcall
typedef struct{char b;char g;char r;char a;} RGBQUAD_;
typedef struct{
BYTE *(DLL_CALLCONV_ *FI_GetBits)(void *dib);
BYTE *(DLL_CALLCONV_ *FI_GetScanLine)(void *dib, int scanline);
BOOL (DLL_CALLCONV_ *FI_GetPixelIndex)(void *dib, unsigned x, unsigned y, BYTE *value);
BOOL (DLL_CALLCONV_ *FI_GetPixelColor)(void *dib, unsigned x, unsigned y, RGBQUAD_ *value);
BOOL (DLL_CALLCONV_ *FI_SetPixelIndex)(void *dib, unsigned x, unsigned y, BYTE *value);
BOOL (DLL_CALLCONV_ *FI_SetPixelColor)(void *dib, unsigned x, unsigned y, RGBQUAD_ *value);
unsigned (DLL_CALLCONV_ *FI_GetDIBSize)(void *dib);
RGBQUAD_ *(DLL_CALLCONV_ *FI_GetPalette)(void *dib);
} dafuq_t;
dafuq_t* dafuq;
FI_GetBits, FI_GetScanLine and FI_GetPalette aren't detected because their return value is a pointer.
Also it doesn't seem like "dafuq" is correctly resolved.. "dafuq->" doesn't popup a member list. (and in case I understood cctest correctly, it also doesn't list its members)

I've run into problems relating function pointers a few times already... but I'm not sure if they were all related to pointer return values like here
Title: Re: The 06 July 2014 build (9844) is out.
Post by: BrianSidebotham on July 25, 2014, 12:12:16 pm
Hey guys,

I'm having trouble with "Project->Properties->Debugger->Additional shell commands->Before connection"

Nothing gets executed from here, instead I have to use "Project->Build Options->Post-build steps" which works fine.

I need these steps for copying the executable to a target machine and launching a remote gdbserver.

Best Regards, Brian.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: BrianSidebotham on July 25, 2014, 03:17:09 pm
Also it appears that breakpoints don't get removed when using remote debugging. I tried just removing them from the scintilla gutter and also using "Remove All" from the breakpoints window, but nothing clears the breakpoints.

Typing delete in the gdb command window works fine however. Thanks so much for thinking of these sorts of things - CodeBlocks is such an excellent IDE!
Title: Re: The 06 July 2014 build (9844) is out.
Post by: oBFusCATed on July 28, 2014, 09:39:12 pm
I'm having trouble with "Project->Properties->Debugger->Additional shell commands->Before connection"
I think this is know problem I have to find time to fix.

Also it appears that breakpoints don't get removed when using remote debugging. I tried just removing them from the scintilla gutter and also using "Remove All" from the breakpoints window, but nothing clears the breakpoints.
Can you post the full log from the debugger (you have to enable it in the settings).
Can you reproduce the problem with simple console project and gdbserver run on a PC, not some embedded device?
Title: Re: The 06 July 2014 build (9844) is out.
Post by: ToApolytoXaos on July 30, 2014, 11:55:59 am
Guys, since svn9851 a very strange behavior appeared with Code::Blocks.

Tab key became 5 spaces instead of 4 without me touching it and for some reason plugin SmartIndentCpp got disabled as well (again!) without me touching any of my settings.

What the...?!

Specs
---------
GNU / Linux Debian testing (32-bit), GCC 4.9.1, wxGTK 2.8.12

P.S.: Right after upgraded from svn9844 to svn9851 it asked me to choose my default compiler for some reason. Is this behavior logical thus far? Cheers
Title: Re: The 06 July 2014 build (9844) is out.
Post by: White-Tiger on July 30, 2014, 10:17:04 pm
[...]
P.S.: Right after upgraded from svn9844 to svn9851 it asked me to choose my default compiler for some reason. Is this behavior logical thus far? Cheers
just in case this wasn't intended... +1 ;) But can't say anything about which rev it was.. just a few days ago. My guess: rev 9851
Title: Re: The 06 July 2014 build (9844) is out.
Post by: ToApolytoXaos on July 31, 2014, 07:52:43 am
Also, there's something's wrong with the parser. I have created an empty project and created a header file and it would not suggest anything as I type, only my own header's name with Ctrl+Space; all I see is that message about parser still parsing. I manually forced it to reparse the entire project and still the issue remained the same. In source file though everything worked okay.

This issue is with svn9853; i haven't tested with svn9851.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: oBFusCATed on July 31, 2014, 09:38:19 am
@Alpha: Do you know why it is asking to set the default compiler? It happens after an upgrade from 9848 to 9853...
Title: Re: The 06 July 2014 build (9844) is out.
Post by: BrianSidebotham on August 01, 2014, 04:03:43 pm
I'm having trouble with "Project->Properties->Debugger->Additional shell commands->Before connection"
I think this is know problem I have to find time to fix.

Excellent, no problem then.

Also it appears that breakpoints don't get removed when using remote debugging. I tried just removing them from the scintilla gutter and also using "Remove All" from the breakpoints window, but nothing clears the breakpoints.
Can you post the full log from the debugger (you have to enable it in the settings).
Can you reproduce the problem with simple console project and gdbserver run on a PC, not some embedded device?

Some further information:

(1) This only happens for remote debugging, debugging the same target on Windows in the same fashion works fine.

(2) Only breakpoints that are created offline, or in other words before debugging is started cannot be removed. On Windows when I set a breakpoint in the code and then start debugging, if I remove that breakpoint I see the command: [debug]> delete breakpoints 3. Under remote debugging the breakpoint gutter icon is removed, but I don't see any command produced in the GDB session.

I hope that makes sense, it's easier than giving a noisy log of GDB activity. Let me know if there's any more information I can provide for you.

Best Regards, Brian.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: oBFusCATed on August 01, 2014, 10:32:48 pm
Have you tried to reproduce the problems with running remote debugging against gdbserver started on a windows pc. I think it is possible and this is the only way I can reproduce them and probably fix them.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: ollydbg on August 03, 2014, 10:38:33 am
@Alpha: Do you know why it is asking to set the default compiler? It happens after an upgrade from 9848 to 9853...
I also have this issue when I update to 9854 nightly.
Title: Re: The 06 July 2014 build (9844) is out.
Post by: Alpha on August 03, 2014, 02:11:52 pm
Oops, missed that question :-[ .  If I correctly remember, that dialog is triggered whenever batch compiler autodection is run (e.g. some compiler(s) are registered without previous existence in the conf file).  The intent there was that these new compiler settings could potentially be incorrect (due to automatic algorithms), so alerting the user of changes is probably best.

I will have to check back into the code later for further details...
Title: Re: The 06 July 2014 build (9844) is out.
Post by: oBFusCATed on August 03, 2014, 02:47:59 pm
Makes a bit of sense, but there is no explanation why this happens presented to the user or at least it is not clear enough. So we as users get confused/annoyed quite a lot.