Author Topic: some bugs found ( may be known )  (Read 4181 times)

violett

  • Guest
some bugs found ( may be known )
« on: November 14, 2011, 01:00:48 pm »
Hello Community,

found several bugs and a feature lack that I leaned to keep in mind using codeblocks 10.05 rev 0 ( build 30 may 2011 )
Could someone direct me to which resource should I place them or they are
already known ( or even solved ) to the date.

1) Having enabled the option "Compiler and debugger settings" -> "Debuigger settings" -> "Catch C++ exceptions"
 as it is by default, codeblock debugger doesn't show me the position in the code until I  continue execution and reach
another breakpoint.

gdb -v
GNU gdb (GDB) 7.1-ubuntu

2) When the target project in the workspace depends on the static library project, and I change code in static library and
do "Build Workspace", only that library is rebuilt, the target seems to be up-to-date to the build system.

3) Codeblock's configuration and projects are saved on gracefull exit, not when it crashes. But it crashes regularily in one case out of 20
when build is started. Could you consider saving the configuration before the build process?

4) It could be hard to recognize the build problem without raw compiler and linker logs, including command line prepared and executed.

5) lack of F6 as in VS: when searching some code it's often quicker to switch between tabs lately accessed rather than use the Jump history.

6) When I accidentally close the console for the debugged program, the program remains running, CB seems to have no control over it anymore,
and the state "debugging is on" cannot be changed. Only restart of CB helps.

7) Is it possible to build inverted index on project files to speed up the search through the workspace files?

8) If external version control tool changes the permissions of an opened file ( checkout ),
CB doesn't know about it. But I can right-click casting the context menu, and attributes will be re-read, allowing me to modify the file.

PS All this feedback was made after I have been using CB for about a month. Everything is almost fine with exceptions like described above.


Online oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11724
    • Travis build status
Re: some bugs found ( may be known )
« Reply #1 on: November 14, 2011, 02:16:31 pm »
For all debugging problems please try a debugger branch nightly.

2) When the target project in the workspace depends on the static library project, and I change code in static library and
do "Build Workspace", only that library is rebuilt, the target seems to be up-to-date to the build system.
Search for external dependencies in the forum.

4) It could be hard to recognize the build problem without raw compiler and linker logs, including command line prepared and executed.
Search for full log in the forum or read the FAQ in the wiki.

5) lack of F6 as in VS: when searching some code it's often quicker to switch between tabs lately accessed rather than use the Jump history.
What does F6 do in VStudio?

And next time please use the correct sub-forum. http://forums.codeblocks.org/index.php/topic,14048.0.html
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: some bugs found ( may be known )
« Reply #2 on: November 18, 2011, 01:22:54 am »
5) lack of F6 as in VS: when searching some code it's often quicker to switch between tabs lately accessed rather than use the Jump history.
What does F6 do in VStudio?
A search says F6 switches focus between the panes of a split editor (source).