User forums > Using Code::Blocks

Upgrading a Windows (binary) installation

<< < (2/2)

dmoore:
isn't #2 related to #1? (you can't debug because you can't successfully build?)

on #1, are you sure you are running the same compiler? presumably the .s files are assembler files, and gcc should understand them without any help from C::B. have you tried to compile from that file from the command line? You might want to switch on full compiler logging (in settings -> compiler and debugger) to see what is getting called by C::B.

MortenMacFly:

--- Quote from: johne53 on February 07, 2009, 07:04:25 pm ---Can anyone help here??

--- End quote ---
If you have never compiled them before disable the compilation in the project settings of the target(s) in question.

johne53:
I went back to the previous version and noticed that the particular module was listed with a "grayed out" appearance and previously, it was obvioulsy never getting compiled. Fortunately, that didn't matter because it was only relevant (i.e. only ever required by the linker) on the ARCH_86 platform. For the time being I've taken your advice and removed it from all targets.

Having said that, the debugger still won't run, even for a very simple app. The red button lights up (as though it is running) but it never launches the app or reaches any break points. However, I'm seeing these two lines in the debugger output window which I don't normally see:-


--- Quote ---> catch throw
Catchpoint 1 (throw)
--- End quote ---

Is that an indication that something's wrong?

Jenna:

--- Quote from: johne53 on February 08, 2009, 04:40:46 pm ---I went back to the previous version and noticed that the particular module was listed with a "grayed out" appearance and previously, it was obvioulsy never getting compiled. Fortunately, that didn't matter because it was only relevant (i.e. only ever required by the linker) on the ARCH_86 platform. For the time being I've taken your advice and removed it from all targets.

Having said that, the debugger still won't run, even for a very simple app. The red button lights up (as though it is running) but it never launches the app or reaches any break points. However, I'm seeing these two lines in the debugger output window which I don't normally see:-


--- Quote ---> catch throw
Catchpoint 1 (throw)
--- End quote ---

Is that an indication that something's wrong?

--- End quote ---

Try it with "Settings -> Compiler and debugger... -> Debugger settings -> Catch C++ exceptions" turned off.
On my system (debian 64-bit) C::B crashes if I have it checked, but my app does not make use of exceptions.

I did not try to find out the cause for the crash, because there are some other things I work on at the moment.

johne53:
Thanks Jens. That seems to have done the trick. My (very small) test app was much too simple to be throwing exceptions so I don't know what the problem might be.

Navigation

[0] Message Index

[*] Previous page