Re: [Dev-C++] Re: Dev-cpp-users digest, Vol 1 #1887 - 11 msgs

[Emiliano <sky...@fa...>]

----- Original Message ----- 
From: "Jens Tusche" <Tu...@gm...>
To: <dev...@li...>
Sent: Monday, February 16, 2004 8:59 AM
Subject: [Dev-C++] Re: Dev-cpp-users digest, Vol 1 #1887 - 11 msgs


> < Subject: [Dev-C++] Debugger not working? 4.9.8.7
> <
> <As in the subject, it won't work at all on my winxp system. The project
> gets
> <compiled, the debugging window is there, but no "step" button does what
it
> <should, the step-by step execution doesn't start. In the output of gdb
I've
> <noticed this:
> <
> <frames-invalid
> <
> <What is the last version with debugger know to work?
>
> This sounds like the problem that I had. It seems that the debugger must
be
> manually coerced to generate the necessary debug information. Somebody
told
> me to put a "-g3" as a parameter to the compiler options. After I'd done
this
> everything has been working fine.

First of all, thank you very much for your answer. I was loosing hope on
this mailing list :)

I've noticed that option was already present in the compiler prompt. I've
also tried to add it as you suggested, but I still get the same problem.

this is the complete gdb output:

(gdb)
prompt
post-prompt
breakpoints-invalid
Breakpoint 2 at 0x40169c: file main.cpp, line 202.
pre-prompt
(gdb)
prompt
post-prompt
Starting: "path/name.exe"

Snooping with FileMonitor, I've noticed that there's an executable starting
somewhere, but then nothing happens (no steps, no window opening, and so
on...). The only effect is that debug window gets ghosted when I click twice
on "Next Step" or "Debug" itself. Everything else simply does nothing.

Also, if I open the cpu window, it goes in "wait timeout for debug command"
error. As if the debugger is not there anymore...

What can I do? :)

regards
Emiliano Esposito