dev-cpp-users

[Dev-C++] Cygnus Insight debugger

[Luigi S. <gi...@li...>]

Hello ,

I have installed the Cygnus Insight debugger, and tried to debug a simple 
console mode application (the "hello world").

When I click the debug icon from the Dev C++ IDE (vers. 4) among the other
windows (source, console, ...) a "warning" pops up, it says:

GDB (title of the window)
i386 architecture file may be incompatible with i386:intel target

Then when I click on the run icon (in the source window) the program hangs.

I've already tried to reinstall the Cygnus Insight debugger and then both
the Dev C++ and Cygnus Insight debugger, but this is of no help.

Does anybody know what is going on?

--
gisan

Re: [Dev-C++] Cygnus Insight debugger

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

Luigi -

> I have installed the Cygnus Insight debugger, and tried to debug a
simple console mode application (the "hello world").
> When I click the debug icon from the Dev C++ IDE (vers. 4) among the
other windows (source, console, ...) a "warning" pops up, it says: GDB
(title of the window) i386 architecture file may be incompatible with
i386:intel target...

First be sure that you have downloaded the Insight version 5 debugger
from http://www.bloodshed.net/dev/.  There are enormous improvements
over the earlier version and it is configured to work with Dev-C++ on
Windows machines (if that is what you are running).  Well, it's not
perfect but it crashes far less often.

> Then when I click on the run icon (in the source window) the program
hangs.

What message do you get in the Console Window when that happens?  What
happens when you enter RUN in the console window?  Verify that the
Target is set to EXEC in the Target Selection area.  From the Source
Window click on File, then Target Settings.

Chuck

Re: [Dev-C++] Cygnus Insight debugger

[Luigi S. <gi...@li...>]

Hello Chuck -

First of all: thank you for answering.
I did not solve the problem yet.
Here are the answers to your questions.

To begin with, this is the code that I'm debugging:

hello.cpp
---
#include<iostream>

int
main()
{
    cout << "hello world\n";
    return 0;
}
---

At 10.26 01/07/01 -0700, you wrote:
>Luigi -
>....
>
>First be sure that you have downloaded the Insight version 5 debugger ...

- I'am working with Win98, "hello" was compiled by Dev C++ version 4 - and 
I have Cygnus Insight Debugger version 5 (help-about says: this GDB was 
configured as "i686-pc-cygwin")


>What message do you get in the Console Window when that happens?

- I get no message in the console window when I start the debugger, but when
I start the program "hello" from the source window, the console window says:

Argument required (target name) try 'help target'
Breakpoint 1, main() at //c/hello/hello.cpp:6

Of course at this point the program is hanged and the only thing I can do 
is kill the source window (which kills the debugger).


>What happens when you enter RUN in the console window?

- the program "hello" executes as expected (strange isn't it ?!)


>Verify that the
>Target is set to EXEC in the Target Selection area ...

the target was initially blank, but selecting EXEC is of no help.


--
gisan

Re: [Dev-C++] Cygnus Insight debugger

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

Luigi -

> - I'am working with Win98, "hello" was compiled by Dev C++ version 4 -
and I have Cygnus Insight Debugger version 5 (help-about says: this GDB
was configured as "i686-pc-cygwin")

That is the same as my installation (except that I am running Windows
95).  The "i686..." part is what you should have.

> >What happens when you enter RUN in the console window?
> - the program "hello" executes as expected (strange isn't it ?!)

Yes, that is exactly what was happening to me...

>>>Argument required (target name) try 'help target'

...until I actually read the 'help target' section of the online
documentation.  That led me to the...

>Verify that the Target is set to EXEC in the Target Selection area ...
> the target was initially blank, but selecting EXEC is of no help.

At this point our paths diverge.  Try selecting EXEC again.  Once I did
that the RUN icon in the Source Windows works every time.  What is
strange is that if I go back to select EXEC the window is blank!  I
would think that EXEC should always appear there until set to some other
value.  I think that's a bug.

Perhaps there's some small feature that is different between our setups.
Before I found the EXEC help suggestion I always had to type RUN into
the Console Window.  It was very cumbersome.  Perhaps you're stuck with
that option until the next revision of the software.

Chuck