User forums > Help

Problems using C::B / GDB under WinXPSP2

(1/2) > >>

Diego:
Hi All!

I am a new C::B user. I've downloaded the latest version (1.0-RC1-1) for Win. And I am running it on a Sempron Mobile 1.6GHz, 256MB RAM with XP SP2 OS.
 
The IDE looks great!!!   :D

 But unfortunately I am having problems trying to debug a simple console application. The GDB seems to suddenly crash after passing some breakpoints.

I have no experience using GDB so I am enterely relying on the C::B interface.

Here is a portion of the GDB dump:

frame-source-end
source C:/DOCUME~1/Diego/MYDOCU~1/CSC545/SIMPLE~1/code/main.c:84:2325:beg:0x402369
frame-end
stopped
pre-prompt
prompt
> next
post-prompt
starting
frames-invalid
frames-invalid
frames-invalid
frames-invalid
frames-invalid
frames-invalid
.
.
.

The GDB (Debug) windows keeps showing 'frames-invalid' message until I manually finish the debugging.

I have been looking to other postings and nobody seems to have the same problem, so I suspect that maybe I am missing something, some configuration or so...

Any Idea about what can be happening?   BTW, GDB is Version 6.3

Thank you!!!!!!!!
Diego.

mandrav:
Haven't seen that before.
One thing you can do is try and create  minimal test-case and post it here with steps to reproduce the problem.
Or, you can downgrade gdb to a more stable version like 5.2 (although I never had any problems with gdb6.3, but that's just me)...

rickg22:
The frames-invalid is a normal message, i think. GDB 6 has this obnoxious habit of saying everything and cluttering the output. But otherwise than that, what do you mean with "crash"?

Diego:
Hi,

What I mean by 'crash' is, for example: the program stops at a breakpoint, then I press F7 (Step over) then the Blue highlighting dissapears and the GDB (Debug) window

keeps showing 'frames-invalid' message over and over while the CPU usage is 100% until I manually stop the debbuging process (Debug->Stop Debbuger).

Thanks for your help,
Diego.

rickg22:
Oh, it means your program probably ran into a loop and Code::Blocks is just reporting the gdb messages. Try "step into" instead and see what happens. But yeah, i think GDB 5.2 sends less messages.

Navigation

[0] Message Index

[#] Next page