Fellows:
I don't know if this would help fix the problem, but find below some
more information on the crash. For more detailed information I would
have to recompiled QtCreator in debug mode, but the output below hints
(I hope) to the source/location of the crash, namely:
Program received sign
Fellows:
I happened to come across a rather unusual crash of QtCreator under
RHEL5. I will try to explain the steps to reproduce the crash:
1) Go to a function implementation line, like:
int FooClass::FooFunction(int const& i, int const& j,
int const&
Note that endl includes an implicit flush, so this isn't really news.
Buffered I/O is buffered I/O and you should never write code that
depends on buffered I/O being output before an explicit flush.
By the way, IIRC, fflush(stdout) should work for stdio.h I/O.
/s/ Adam
On Sat, Apr 24, 2010 at 4
Thanks, Charles.
Paul
On Sat, Apr 24, 2010 at 4:10 PM, Charles N Burns
wrote:
> Try this:
> http://www.formortals.com/build-qt-static-small-microsoft-intel-gcc-compiler/
>
> On Sat, Apr 24, 2010 at 5:20 AM, Paul Smith wrote:
>> Dear All,
>>
>> How to produce an executable with static libraries
On 24 Apr 2010, at 22:22, Robert Hairgrove wrote:
>>
>
> This is also an issue in non-Qt apps. Just change this line:
> std::cout << "test";
> to this:
> std::cout << "test" << std::endl;
>
> On some platforms (*nix, I think) you need to do this in order to keep
> the next output fro
OSX 10.6.3 Leopard, Qt 4.6.2, Creator build 1.3.83 (rev 026237b008).
pro:
SOURCES += main.cpp
CONFIG += console
Build log:
Running build steps for project ArrayTest...
Starting: /usr/bin/make clean -w
make: Entering directory `/Users/ks/Projects/ArrayTest-build'
rm -f main.o
rm -f *~ core *.c
Danny Price wrote:
> Definitely an issue here. I created a C++ project and added CONFIG +=
> console to the pro file. The following does NOT print to the console
> until after main returns (as shown with a breakpoint)
>
>
> #include
> int main()
> {
> std::cout << "test";
> return 0;
> }
Thi
Strange, as was expected, works for me. Could you please attach the
console output of your compiler. And give the information about your
environment.
Thank you.
On 2010/04/24, at 21:25, Danny Price wrote:
> Definitely an issue here. I created a C++ project and added CONFIG
> += console to
Definitely an issue here. I created a C++ project and added CONFIG += console
to the pro file. The following does NOT print to the console until after main
returns (as shown with a breakpoint)
#include
int main()
{
std::cout << "test";
return 0;
}
However if I add cout.flush()
On 19 Apr 2010, at 17:33, Tobias Hunger wrote:
> On 19.04.2010 18:02, ext Danny Price wrote:
>> I think the settings in the .pro file should always take priority. This
>> is allows for automated builds and builds outside of Creator.
>
> I do not get your point here: Of course the pro-file gets p
Try this:
http://www.formortals.com/build-qt-static-small-microsoft-intel-gcc-compiler/
On Sat, Apr 24, 2010 at 5:20 AM, Paul Smith wrote:
> Dear All,
>
> How to produce an executable with static libraries?
>
> Thanks in advance,
>
> Paul
> ___
> Qt-cre
Dear All,
How to produce an executable with static libraries?
Thanks in advance,
Paul
___
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator
12 matches
Mail list logo
