User forums > Help

Debugging with external debugger

<< < (2/3) > >>

mandrav:

--- Quote from: Curtisc on May 25, 2006, 05:47:45 pm ---Ok... now I'm just creating a new project, and every time I try to add files to it it crashes.  Maybe the old version is more stable?

--- End quote ---

What OS are you using? There have been some other posts about linux crashes when adding/removing files. I can't remember the distro though. I think it was either Gentoo or Suse...

Curtisc:
I'm running Ubuntu (Dapper).

The crashing seems to be fairly random - I'll add a file and it will be fine, then I try another and it will crash.  Then I can restart it and try again, and the one that worked the first time will cause the crash!  If I try and recursively add a folder of files, it's guaranteed to crash.

I'm not adding new files, I'm adding files that already exist.  Maybe if I add new files and copy the code over from gedit or something?  I might try that tomorrow.  It would still be nice to have the problem resolved.

In detail, Amira creates a directory structure that it likes, and creates a GNUMakefile.  It also creates some default files (ProjectName.h, ProjectName.cpp, Version.h, etc), which I have written over with source code copied from the same project that was compiled for windows.  Then, in C::B, I created a new cb project in the same directory, and when I try to add my source code files, I get the crashing thing.  It also crashes when I try to attach the debugger to Amira.  I also tried importing the old VC++ 6.0 file, and that made it crash.

Would there be a crash log generated somewhere?  The only thing I could find was /tmp/Code::Blocks-charlotte, and it didn't seem to contain anything.

It's funny I'm having so many problems, I'd expect this to be a relatively common thing to do.  Hopefully I can figure out what's causing it - I like the looks of C::B more than the others I've tried (Anjuta and Eclipse).

mandrav:

--- Quote ---I'm running Ubuntu (Dapper).
--- End quote ---

--- Quote ---It's funny I'm having so many problems, I'd expect this to be a relatively common thing to do.
--- End quote ---

Yeah, strange. Especially Ubuntu has been extensively tested (Breezy though).
Have you tried disabling the code-completion plugin (you have to restart C::B then)? There have been some changes there lately and I wouldn't be surprised if it was the problem...

Michael:

--- Quote from: mandrav on May 26, 2006, 08:23:45 am ---
--- Quote ---I'm running Ubuntu (Dapper).
--- End quote ---

--- Quote ---It's funny I'm having so many problems, I'd expect this to be a relatively common thing to do.
--- End quote ---

Yeah, strange. Especially Ubuntu has been extensively tested (Breezy though).
Have you tried disabling the code-completion plugin (you have to restart C::B then)? There have been some changes there lately and I wouldn't be surprised if it was the problem...

--- End quote ---

Yes, it is quite strange :?. Ubuntu is relatively stable (at least 5.10). I will give it a look later, as now I have some crashes in my project's application :).

Best wishes,
Michael

Curtisc:
Success (sort of)!

Since I'm not actually developing anything at the moment, I figured I didn't need most of the plugins, so I disabled them all except for the compiler and debugger.  No more crashing problems - definitely a plugin issue.  Now I just need to figure out how to configure C::B to use Amira as an external debugger.  I tried just running Amira and attaching my module to the PID, but Amira just hangs and I can't load the module.  Is there some way to configure an external debugger?

Navigation

[0] Message Index

[#] Next page

[*] Previous page