Recent Posts

Pages: 1 ... 5 6 7 8 9 [10]
91
Please read http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28general%29#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F

1. Make sure you have an FORTRAN Compiler installed.

Edit: Code::Blocks is an IDE/Editor; it is NOT a Compiler

Tim S.
92
Help / Re: Graphical interface issue on Ubuntu Xenial
« Last post by devsh2 on April 21, 2017, 05:06:13 pm »
This bug affects Ubuntu 17.04 Zesty as well, and I cant get anything from the PPA because of dependency conflicts (even when I try to use the xenial channel in software sources)

Is there an ETA on a zesty package??
Or some sort of a guide to compiling with wx2.8 ?
93
Hi all,

I am new to Code Blocks but not to FORTRAN. I am writing a CODE in FORTRAN but when I press Build and Run button, it gives the following error;

||=== Build file: "no target" in "no project" (compiler: unknown) ===|

Please help me out.

Thank you all in anticipation.
94
General (but related to Code::Blocks) / Re: build codeblocks with wxWidgets3.1.0
« Last post by oBFusCATed on April 21, 2017, 02:33:28 pm »
It is GCC's bug, not wx' bug.
Please don't make such accusations without a thorough investigation!
95
Help / Re: crash when use wxsmith
« Last post by oBFusCATed on April 21, 2017, 02:26:22 pm »
The true crash site is the first post, and I attached the picture. I think @jens is right, the similar question of gcc
http://forums.codeblocks.org/index.php/topic,21773.0.html .
Sorry, but do you think you can solve the problem with the information provided in the first posts?

GCC is very solid compiler and it is very hard to find bugs in it.
Most of the times the problems are caused by bugs in the program that are manifested by an aggressive optimization.
These are still bugs in the program and not in GCC!
96
Help / Re: crash when use wxsmith
« Last post by oBFusCATed on April 21, 2017, 02:22:53 pm »
It might be an(other) optimization bug of gcc.
These are not bugs, but features :)
Lets see if I can reproduce this in wx2.8 and gcc 6.x.
97
Help / Re: crash when use wxsmith
« Last post by icequan233 on April 21, 2017, 02:00:12 pm »
This is not the crash site as far as I can tell, isn't it?
Please remove all breakpoints and let it crash.
Then go to the call stack window, right click in the window and click on the copy to clipboard menu item.
Then paste the callstack in a code or quote tags.
The true crash site is the first post, and I attached the picture. I think @jens is right, the similar question of gcc
http://forums.codeblocks.org/index.php/topic,21773.0.html .
 
98
Help / Re: crash when use wxsmith
« Last post by jens on April 21, 2017, 01:29:04 pm »
The crash happens because of an illegal pointer in propgrid.cpp (GetY2) in the for-loop.
getParent returns 0xfeeefee.
I can reproduce it with wx2.8 and wx3.
It either tries to access an already deleted or an incorrect initialized pointer, looking at the address, the first is more likely.
It might be an(other) optimization bug of gcc.
99
Using Code::Blocks / Re: AStyle button in toolbar
« Last post by oBFusCATed on April 21, 2017, 01:00:23 pm »
By writing a plugin which creates its own toolbar.
Unfortunately this is the only option at the moment.
100
Help / Re: crash when use wxsmith
« Last post by oBFusCATed on April 21, 2017, 12:59:33 pm »
This is not the crash site as far as I can tell, isn't it?
Please remove all breakpoints and let it crash.
Then go to the call stack window, right click in the window and click on the copy to clipboard menu item.
Then paste the callstack in a code or quote tags.
Pages: 1 ... 5 6 7 8 9 [10]