User forums > Nightly builds

The 09 August 2008 build (5182) is out.

<< < (4/6) > >>

Belgabor:
The first type of crash does not create a RPT and for the second one I posted the results above.

Pecan:

--- Quote from: Belgabor on August 15, 2008, 06:56:57 pm ---The first type of crash does not create a RPT and for the second one I posted the results above.

--- End quote ---

You might catch these crashes by running CodeBlocks under gdb within a console window.
Start a cmd window, and issue "gdb --args codeblocks" .

When the crash happens do a "backtrace full" in the cmd window and keep hitting enter to get all the info.

Mark/copy/paste the cmd window to an editor and paste it here.

Be sure that the cmd window has some part of itself visible, else it might  get hidden behind the CodeBlocks window when the crash happens.

MortenMacFly:

--- Quote from: Pecan on August 15, 2008, 07:31:28 pm ---You might catch these crashes by running CodeBlocks under gdb within a console window.
Start a cmd window, and issue "gdb --args codeblocks" .

--- End quote ---
Notice that this makes most sense if you did not strip the symbols. But on Linux (IMHO) this s not the case anyways...?!

mpupro:
If I use "Debug\Run to cursor", my cb(svn 5182) will show these messages and stop running:

Setting breakpoints
Debugger name and version: GNU gdb 6.8
Child process PID: 2420
At C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/c++/3.4.5/iostream:77

If I press Ctrl+F7 to continue:

Continuing...
At C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/c++/3.4.5/iostream:77

No such problems in CB 8.02, I use it to compile "Ogre+mingw" projects.
Thanks

indigo0086:
I have a problem with breakpoints.  When I set a breakpoint, then press debug, it will not stop at the breakpoint right away, I have to press it again to go to the first one.

Navigation

[0] Message Index

[#] Next page

[*] Previous page