User forums > General (but related to Code::Blocks)

C::B crashes after Debug - Next Line

<< < (3/3)

benezan:
Now, I have deleted everything, once again, and re-installed with TDM-GCC-32 V4.8.1. I re-built every library from clean state and now it seems to work. I can step through the code line by line with the debugger, again. :)
I still have to check if everything else works. I've got a few more warnings than usual from the compiler.
But at least it's definitely not a problem of Code::Blocks.

Thanks for your help, I hope I don't need any more of it.

benezan:
Grrr, spoke too soon. The problem is still there. :( It just moved to different parts of the source. It seems that with the new compiler the adress ranges where the code is located is mixed up a bit. "Next line" works now at the breakpoints I used to set before but I get input/output errors again when I step through the code at different locations.

I double checked for duplicate installations of gcc*.exe and gdb*.exe. There was a path "C:\Programme\AlteraQuartus\quartus\bin" with gcc in the environment variable PATH. I renamed bin to bin-test before the last re-build (a complete re-build of wxWidgest and all other dlls I use).

Could it be that a strange bug in my code overwrites some adresses on the stack? But why does it work with "run to cursor"? When I use this with the cursor on the next line it should set the exact same breakpoint and execute the exact same code accessing the exact same memory. ???

A friend also suggested it could be a memory problem with my PC. But I get the same messages with the same adresses reported on two different PCs with different processors and different DRAM brand. The only common thing is that Windows was installed from the same CD.

oBFusCATed:
If it is exactly the same error after multiple runs and recompiles then it is not cause by a bad memory.

Have you tried if this same thing happens if you use gdb on the command line?
If it does it will be best to contact the support channels (mailing list or irc channels) for mingw or gdb, they can give you better hints about what is going on.

Navigation

[0] Message Index

[*] Previous page