User forums > Nightly builds

The 09 August 2008 build (5182) is out.

<< < (5/6) > >>

Pecan:

--- Quote from: indigo0086 on August 19, 2008, 02:23:55 pm ---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.

--- End quote ---

Try unticking  Settings/Compiler&Debugger/Debugger Settings/Catch C++  exceptions.

It works on my svn build  rev 5177 (2008-08-01T17:17:35.636485Z)   gcc 3.4.5 Windows/unicode

indigo0086:
Works great, thanks.

ftfish:

--- Quote from: mpupro on August 16, 2008, 04:13:06 am ---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

--- End quote ---


Same problem with "Run to cursor" here, but my CB didn't stop running after pressing F4. Instead, my CB entered debug mode but no console appeared.
So it forced me to use cstdio instead of iostream.
Hope it be solved.

three_minute_hero:
Hi everyone,

Sorry, one more bad news :(
I'm using CMake with C::B generator, so I regularly have to reload the project after a modification of the CMakeLists.txt.
It doesn't happen every time, but when I reload the project, C::B may crash silently. The console shows a segmentation fault message only, with no other information.

When running with gdb, I got this:

--- Code: ---Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6641700 (LWP 7201)]
0xb683c8fc in ?? () from /lib/i686/cmov/libc.so.6
--- End code ---
Not so instructive :?

Crash happens (at least) in the following use case:

* Two projects have to be open (e.g. a library project and its unit tests' project)
* The library project must be open first, unit test second
* Run CMake to update library project file
* Reload project in C::B
* EnjoyNo crash when updating unit tests' project…

I'm using Debian Sid.

I'm available for any further information you may need.

bianxiaobin2006@163.com:
the link (http://download.berlios.de)maybe wrong !

Navigation

[0] Message Index

[#] Next page

[*] Previous page