User forums > Help
Several show-stopping problems
ikolev:
Hi guys.
I have a few serious problems with Code::Blocks, which are about to make me look for another GCC-based development environment for Windows (Dev-Cpp seems the only choice, Eclipse is tragic). I download each new nightly build in hope that they may be fixed, but it seems they are not known, so I decided to post here (I can also post bug reports on the BerliOS if required).
I have two major projects that I work on in C::B. Both were imported from VC7.1 solutions. One is an open source library ( http://www.ikolev.com/DebugTools/ ) and consists just of two projects, one for the static library and one for the unit tests executable (which in C::B could be made targets, but I prefer the MS approach of a single project for each target, with several debug/release/etc. configurations). The other one is a large private project with several libraries (static and dynamic) and executables.
Here are the problems:
- First of all, of course, are the regular crashes. They happen mostly when switching projects/workspaces. Sometimes the new workspace is loaded successfully, but a crash occurrs when hitting Build (Ctrl-F9). I can upload the .rpt file if that can help.
- A non-fatal but quite unpleasant problem is the random change of project dependencies when loading a workspace. Unfortunately this happens only with the private project, so I can't post an example workspace. It also happens occasionally, it's not 100% reproducible. There are 9 projects in the workspace. Sometimes dependencies get so messed up, that when I hit Build for some project, C::B builds another one. Deleting all temporary build directories and the project .layout and .depend files and building from scratch fixes it.
- The most important problem is the impossibility to debug from the IDE. I have set all needed options (compiler debug info etc.), and I am able to debug with gdb from the command line. However, that's quite unproductive. I think the problem is (almost) the same as described by klight in this thread http://forums.codeblocks.org/index.php?topic=2509.0 . Any breakpoints I set are listed as "pending" by gdb and never resolved. Also, I cannot single-step in the source code. With the larger project the executable doesn't even start, it just hangs. With DebugTools at least the program starts and finishes successfully, but I cannot debug it.
I can upload all source code and project files for DebugTools if required.
And in the end, a minor problem. In these projects I also have a "commands only" target called "RunTests" which is intended just to start the unit test executables. They contain built-in DOS commands like "cd" which won't work. I need to use "cmd /c cd ...", and of course this doesn't keep the current directory between commands, unless I use "cmd /c cd someDir & someExe & anotherExe".
Please let me know if I can do anything to help resolve the debugging problem in first place. I would have tried to debug C::B myself, but I cannot since debugging doesn't work :) I considered porting the C::B project files to Visual C++ so I can debug it there (besides, the VS debugger is very, very good), but I found that it would require a lot of source code changes. If there is interest in this, I could spend some time porting C::B to Visual C++.
mandrav:
--- Quote ---I download each new nightly build in hope that they may be fixed, but it seems they are not known
--- End quote ---
And they will remain unknown if noone reports them.
--- Quote ---- First of all, of course, are the regular crashes.
--- End quote ---
Regular crashes... Hmm... I can't give you much help since I seldomly experience any crashes here (in three PCs, two win32 one linux64) and if I do I almost immediately fix it and commit.
Try disabling the code-completion plugin. It's the only known source of crashes...
--- Quote ---- A non-fatal but quite unpleasant problem is the random change of project dependencies when loading a workspace.
--- End quote ---
Once again, having never experienced it, I can't be of much help (yes, I do work with large workspaces). Your best bet is to create a minimal reproducible test-case and send it to us describing the steps to reproduce.
--- Quote ---- The most important problem is the impossibility to debug from the IDE.
--- End quote ---
You can't debug anything, or your projects in question?
--- Quote ---And in the end, a minor problem.
--- End quote ---
Why don't you create a batch file (say, runtests.bat) and call this from your commands-only target?
--- Quote ---I considered porting the C::B project files to Visual C++ so I can debug it there (besides, the VS debugger is very, very good), but I found that it would require a lot of source code changes. If there is interest in this, I could spend some time porting C::B to Visual C++.
--- End quote ---
I think that my earlier reply on a similar question should answer this.
For the end, I left your opening sentence that I 'd like to quote:
--- Quote ---I have a few serious problems with Code::Blocks, which are about to make me look for another GCC-based development environment for Windows (Dev-Cpp seems the only choice, Eclipse is tragic).
--- End quote ---
(emphasis added by me)
I 'm really confused by this very sentence...
Dev-Cpp is a nice little IDE (windows-only, gcc-only) which is good for small scale projects.
But you got me confused here: you 're talking about problems with C::B regarding large workspaces with multiple targets per-project, inter-project dependencies on a workspace level and whatnot.
Newsflash:
Dev-Cpp does not support any of these features.
So, what is exactly the point you 're trying to make with this sentence?
Yiannis.
squizzz:
Hi,
At some point (when I started using nightly builds, to be exact) I've experienced pretty much all of the problems you mention. The reasons of these problems were trivial, so let me shortly pinpoint them. Maybe it helps you solve yours.
--- Quote from: ikolev on March 11, 2006, 11:27:13 am ---- First of all, of course, are the regular crashes. They happen mostly when switching projects/workspaces. Sometimes the new workspace is loaded successfully, but a crash occurrs when hitting Build (Ctrl-F9). I can upload the .rpt file if that can help.
--- End quote ---
It happened to me because I mixed RC2 version with nightly build (I unzipped nightly build to RC2 directory). It was not only randomly crashing, but many options were working in a weird way.
If that's your case, simply create new, separate directory and unpack nightly builds there. That solved all the oddities here.
--- Quote ---- The most important problem is the impossibility to debug from the IDE. I have set all needed options (compiler debug info etc.), and I am able to debug with gdb from the command line. However, that's quite unproductive. I think the problem is (almost) the same as described by klight in this thread http://forums.codeblocks.org/index.php?topic=2509.0 . Any breakpoints I set are listed as "pending" by gdb and never resolved. Also, I cannot single-step in the source code. With the larger project the executable doesn't even start, it just hangs. With DebugTools at least the program starts and finishes successfully, but I cannot debug it.
I can upload all source code and project files for DebugTools if required.
--- End quote ---
Make sure you use GDB at version 6.3. Got the same behaviour unless I upgraded it. Because GDB 6.3 is at RC stage, there is fair probability that you don't have it yet. You may get it here (check the bottom of the page, in snapshot section)
Hope that helps,
Jan
RJP Computing:
First off, this IDE is the best IDE for GCC hands down. Way to go. I use it daily and it works well. Thanks for all your effort.
I agree with squizzz and ikolev. I had all kinds of weird crashes which seemed to be from me upgrading a RC2 install to the nightly builds. I also found that by changing away from the RC2 MinGW install it helped a lot. I still see periodic crashing when closing Code::Blocks when it has a large project open and it has been open for a long period of time. I have not tried to disable the code=completion plug-in yet. I use that ALL THE TIME. But I definitely could to see if it gave me more stability.
Once again thanks for all the updates and the great IDE.
Michael:
Hello,
--- Quote from: ikolev on March 11, 2006, 11:27:13 am ---I have a few serious problems with Code::Blocks, which are about to make me look for another GCC-based development environment for Windows (Dev-Cpp seems the only choice, Eclipse is tragic).
--- End quote ---
Using a new IDE requires time and practice. If you have a problem with C::B, the best thing to do is first to have a look at the C::B wiki and do a search in the forum. If you find no info, then you can post your problem in the forum (without forgetting your C::B/OS version, which compiler do you use, etc.).
Personally, I find C::B much better than Dev-C++ and Eclipse, but this does not means that they are worthless. I have tried both and you can work with them more or less good, mostly depending on your application requirements.
--- Quote from: ikolev on March 11, 2006, 11:27:13 am ---I download each new nightly build in hope that they may be fixed, but it seems they are not known, so I decided to post here (I can also post bug reports on the BerliOS if required).
--- End quote ---
If you remark/experience problems, you should check in the forum and in BerliOS to see if they have been reported already. If not, you can post your bug in BerliOS.
Best wishes,
Michael
Navigation
[0] Message Index
[#] Next page
Go to full version