dev-cpp-users

[Dev-C++] Insight Under Dev-C++

[Charles <cha...@at...>]

I'm running version 4.01 of Dev-C++ under Windows 95 with the Mingw
2.95.2-1 compiler.  I have also been using version 4.18 of gdb
"configured as i386-mingw32."

Recently I downloaded the Cygnus Insight debugger from the Bloodshed Web
site.  Now I show the gdb version as 19991101 which is "configured as
i586-cygwin32."

Insight exhibits some strange behavior:

a. Sometimes setting a breakpoint at a particular line in one program
module results in the setting of a breakpoint at the same line number in
another module instead.

b. Attempting to view the Memory window causes an invalid page fault and
Insight crashes.

c. The Insight Run, Step, Next etc. buttons do not appear to work.  The
Run, Step, Next etc. commands do work correctly in the Console window
though.

Should I be using the Cygwin compiler instead of Mingw or should I look
elsewhere for the solution to these problems?


Chuck Brockman

Re: [Dev-C++] Insight Under Dev-C++

[Gregor P. <Gre...@dl...>]

Charles wrote:

> I'm running version 4.01 of Dev-C++ under Windows 95 with the Mingw
> 2.95.2-1 compiler.  I have also been using version 4.18 of gdb
> "configured as i386-mingw32."
> ...

I'm using nearly the same tools exept my Dev-C++ version counts 4
I've some trouble with the Insight debugger too.

I) During a debugging session the source-code doesn't get shown anymore.
   This happens most times when I step into a function which is contained in

  a different file than the current one

II) The debugger seems to hang up in a endless loop or something.
     Windows gives me the hour glas while pointing on the debugger
     (I own a 500MHz AMD, 96MB RAM)
    Restarting the debugger somtimes help somtimes don't (it crashes)

Are there any non console alternatives?


Gregor