User forums > Nightly builds
The 27 November 2010 build (6863) is out.
xawari:
//BUGBUG
wxWidgets wizard fails when using "Cygwin GCC" compiler after the "library settings" step. And on the next step too.
Biplab:
--- Quote from: xawari on December 10, 2010, 05:02:54 pm ---//BUGBUG
wxWidgets wizard fails when using "Cygwin GCC" compiler after the "library settings" step. And on the next step too.
--- End quote ---
Cygwin GCC is not supported by wxWidgets wizard.
wodraq:
I found a bug in the code completion. a minimal example is found below.
I want to write fooIter->length();
However after writing fooIter->l the program crashes without an error message.
#include <iostream>
#include <vector>
using namespace std;
int main()
{
vector<string> fooArray;
vector<string>::iterator fooIter;
fooIter=fooArray.begin();
fooIter->
return 0;
}
Jenna:
--- Quote from: wodraq on December 16, 2010, 03:12:50 pm ---I found a bug in the code completion. a minimal example is found below.
I want to write fooIter->length();
However after writing fooIter->l the program crashes without an error message.
#include <iostream>
#include <vector>
using namespace std;
int main()
{
vector<string> fooArray;
vector<string>::iterator fooIter;
fooIter=fooArray.begin();
fooIter->
return 0;
}
--- End quote ---
It does not crash her (debian 64-bit, latest trunk, no cc modifications).
cacb:
Bug report: If you have a project with different targets, using different compilers for different platform targets, then Code::Blocks crashes on Linux if you mention a non-existent default compiler (msvc8) outside the target descriptions. This used to not crash, so I have a few of these cases....
More to the point, I have 4 build targets, using the follwing compilers
W32_Debug : msvc8 (Windows.... obviously)
W32_Release : msvc8
UX_Debug : gcc (Linux)
UX_Release : gcc
A typical project files begins like this
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="cpde_csv" />
<Option pch_mode="2" />
<Option compiler="msvc8" /> <== causes C::B crash on Linux
<Option virtualFolders="libcsv\;" />
<Build>
<Target title="W32_Debug">
... etc.
The red line must be deleted, and all is well after that. However, it is a but tough to crash C::B on this issue, especially since the project file was (at least originally) wizard generated 8) I have workspaces with quite a few project files with this issue and it is annoying to have to open each project separately just to figure out which project file causes C::B to crash ...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version