User forums > Nightly builds
The 18 June 2006 build is out.
Pecan:
For those of you getting the crash... try the following in order to identify the Signal...
Run Codeblocks.exe from within console (dos) with GDB
"gdb codeblocks.exe"
"run"
(when the crash occurs it will tell you what signal occured. Do..)
"bt all" (meaning backtrace)
"q" (meaning quit)
Then paste the results to the forum
EDIT: These sigtraps happend after I installed MSVC on my laptop about a year ago. My old system, which has never had MSVC on it, does *not* get these sigtraps when running GDB.
Denis:
MortenMacFly, Thanks! Sorry for I didn't use forum search before posting :)
royalbox:
@Pecan
I've been learning c++ with code::blocks for about a year, but I don't know what GDB is. Is is something to do with debugging? If you or someone could give a bit more info on it I'll give it a try. I tried it anyway but the computer didn't understand what it was. I'd like to help sort this out.
Pecan:
--- Quote from: royalbox on June 19, 2006, 07:00:03 pm ---@Pecan
I've been learning c++ with code::blocks for about a year, but I don't know what GDB is. Is is something to do with debugging? If you or someone could give a bit more info on it I'll give it a try. I tried it anyway but the computer didn't understand what it was. I'd like to help sort this out.
--- End quote ---
GDB is the gnu debugger used by codebocks and minGW. It will be in your mingw bin directory.
When I debug codeblocks, I always run it from within a dos box (console) so I can see the traps/errs code lines that caused the error. GDB will stop the system when an trap occurs.
I use the following statements to run gdb:
--- Code: ---PATH=%PATH%;c:\usr\codeblocks\bin <== bin directory contains mingw gdb etc
c:\usr\codeblocks\bin\gdb c:\Usr\Proj\cbBeta\trunk\src\devel\codeblocks.exe
--- End code ---
The above will start CodeBlocks and stop with the gdb prompt "(gdb)"
Type "run" and codeblocks will run while gdb monitors it's every move.
If an error occurs, CodeBlocks will halt, and the dos box will show the Signal that occured.
Type "bt all" (meaning) show the stack and all variables on the stack. (assuming compilation was with debugging flag on)
If CodeBlocks was compiled with the debugging flag checked, it will also show the line the error occured on.
Type "q" to quit CodeBlocks and gdb.
Attached is a pdf of gdb commands that you can print out and tri-fold for reference.
[attachment deleted by admin]
royalbox:
@@Pecan
Thanks very much for the info.
I'm using the code::blocks nightlies and the MSVC 2005 compiler. I only have mingwm10.dll. I'll go to the home page and see what I need to get.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version