dev-cpp-users

[Dev-C++] Setting up Insight

[Marc F. <fel...@gm...>]

I keep reading that Insight is a very nice frontend for gdb in
Dev-C++.  When I update Dev-C++, it provides me with the binary for
Insight (I'm using beta 4.9.9.2, btw).  However, it doesn't
self-install and default configure upon downloading, and there are no
obvious instructions on how to configure it to run over the top of
Dev-C++.  I've scoured the net and have located a zipped "package" of
Insight for Dev-C++ that unzips into the correct directories and runs
(sort of) with the latest beta.  However, when I attempt to debug a
program that has no known bugs (a Win32 console program), not only
does Insight barf (it runs the console program but nothing displays
and none of the command buttons are usable), but when I try to exit
from Insight, Dev-C++ goes into an unstable state and has to be killed
completely using CTL-ALT-DEL.  Since the program is quite  clean,
having been fully debugged and cleaned both under Visual Studio and
Borland C++ Builder (and under Linux using gcc 4), there isn't
anything complicated in it that should be causing this behavior.

So, I'm concluding that this set of zipped files is NOT entirely
compatible with the 4.9.9.2 build of Dev C++, but that whatever is
available via the update process within *is* compatible.  So the
question is whether the DEV-C++ installer puts them in the correct
location or simply stores them in a place where the user can then move
them to the proper location.  It surely ain't doing the latter, but
perhaps it is a configuration problem.

Help/advice appreciated.

Thanks.
--=20
Dr. Marc Feldesman
Portland State University
http://web.pdx.edu/~h1mf

If you received this email by mistake, blame my computer, not me.

Re: [Dev-C++] Setting up Insight

[Alfred P. R. <al...@ya...>]

Hi Dr. Feldsman,
 
I find your problem very interesting, as I've not seen this in my use of Dev-C++.  I place the Insight_Binary.DevPak file in the Packages folder of Dev-C++ and allow Packman.exe to install it.
 
Part of the problem may be, and I'm getting this from your description, is that Insight is a stand-alone program.  When I use it, I compile my program with debugging information enabled using Dev-C++.  Then I start Insight outside of Dev-C++ and use it's many useful features.  Then I close Insight and proceed to preform any changes.
 
I am using wx-devcpp-6.7beta_setup, which is a wxwidgets port of Dev-C++, however if I recall correctly, it has been updated for 4.9.9.2 changes.  Please contact me off-list and I can e-mail you the Insight_Binary.DevPak file which is approximately 5,264KB in size.
 
Hopefully the above helps.

Marc Feldesman <fel...@gm...> wrote:
I keep reading that Insight is a very nice frontend for gdb in
Dev-C++. When I update Dev-C++, it provides me with the binary for
Insight (I'm using beta 4.9.9.2, btw). However, it doesn't
self-install and default configure upon downloading, and there are no
obvious instructions on how to configure it to run over the top of
Dev-C++. I've scoured the net and have located a zipped "package" of
Insight for Dev-C++ that unzips into the correct directories and runs
(sort of) with the latest beta. However, when I attempt to debug a
program that has no known bugs (a Win32 console program), not only
does Insight barf (it runs the console program but nothing displays
and none of the command buttons are usable), but when I try to exit
from Insight, Dev-C++ goes into an unstable state and has to be killed
completely using CTL-ALT-DEL. Since the program is quite clean,
having been fully debugged and cleaned both under Visual Studio and
Borland C++ Builder (and under Linux using gcc 4), there isn't
anything complicated in it that should be causing this behavior.

So, I'm concluding that this set of zipped files is NOT entirely
compatible with the 4.9.9.2 build of Dev C++, but that whatever is
available via the update process within *is* compatible. So the
question is whether the DEV-C++ installer puts them in the correct
location or simply stores them in a place where the user can then move
them to the proper location. It surely ain't doing the latter, but
perhaps it is a configuration problem.

Help/advice appreciated.

Thanks.
-- 
Dr. Marc Feldesman
Portland State University
http://web.pdx.edu/~h1mf
<snip>



Alfred P. Reaud
 

Re: [Dev-C++] Setting up Insight

[Vale G. <val...@at...>]

Marc and Alfred -

>> ...when I attempt to debug a program ...not only does Insight barf ...but
when I try to exit from Insight, Dev-C++ goes into an unstable state ...

> Part of the problem may be...is that Insight is a stand-alone program.  When I
use it, I compile my program with debugging information enabled using Dev-C++.
Then I start Insight outside of Dev-C++ and use it's many useful features.  Then
I close Insight and proceed to preform any changes.

I invoke Insight on my programs from within Dev-C++ by configuring a Tool
shortcut.  In the Edit Tool Program field I put:

C:\cygwin\bin\INSIGHT.EXE
(I use the cygwin version.)

My Working Directory field is:

C:\cygwin\bin\

In the Parameters field I put:

"<EXENAME>"
(The quotation marks are necessary.)

After I compile my program I click on Tools > Insight Debugger and Insight comes
up in a separate window ready to run my program.

Chuck

Re: [Dev-C++] Setting up Insight

[Alfred P. R. <al...@ya...>]

Thanks for the info, Vale.  That's a very good solution!

Vale Group <val...@at...> wrote:Marc and Alfred -

>> ...when I attempt to debug a program ...not only does Insight barf ...but
when I try to exit from Insight, Dev-C++ goes into an unstable state ...

> Part of the problem may be...is that Insight is a stand-alone program. When I
use it, I compile my program with debugging information enabled using Dev-C++.
Then I start Insight outside of Dev-C++ and use it's many useful features. Then
I close Insight and proceed to preform any changes.

I invoke Insight on my programs from within Dev-C++ by configuring a Tool
shortcut. In the Edit Tool Program field I put:

C:\cygwin\bin\INSIGHT.EXE
(I use the cygwin version.)

My Working Directory field is:

C:\cygwin\bin\

In the Parameters field I put:

""
(The quotation marks are necessary.)

After I compile my program I click on Tools > Insight Debugger and Insight comes
up in a separate window ready to run my program.

Chuck
<snip>



Alfred P. Reaud