I have the insight from http://www.wxwidgets.org/docs/tutorials/devcpp.htm which is a windows binary.
I put it in my dev-cpp\bin folder and pointed my gdb.exe to insight.exe, the
problem is when I try to debug it compiles but no window opens. Am I going
about this wrong? what should I do differently?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I strongly recommend that you use the Insight build from the User Contributed
section of the MinGW project (here).
Also the GDB integration in Dev-C++ operates GDB in command line mode, so
using Insight in that way will give no particular advantage. The integration
also sucks.
The way I have used Insight with Dev-C++ is to add it as an item on the Tools
menu using the Tools menu customisation feature. There is a macro available
representing the project executable which you can use to pass this to Insight.
Unfortunately there are no macros for passing command line arguments for the
app being debugged.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the insight from http://www.wxwidgets.org/docs/tutorials/devcpp.htm which is a windows binary.
I put it in my dev-cpp\bin folder and pointed my gdb.exe to insight.exe, the
problem is when I try to debug it compiles but no window opens. Am I going
about this wrong? what should I do differently?
I strongly recommend that you use the Insight build from the User Contributed
section of the MinGW project (here).
Also the GDB integration in Dev-C++ operates GDB in command line mode, so
using Insight in that way will give no particular advantage. The integration
also sucks.
The way I have used Insight with Dev-C++ is to add it as an item on the Tools
menu using the Tools menu customisation feature. There is a macro available
representing the project executable which you can use to pass this to Insight.
Unfortunately there are no macros for passing command line arguments for the
app being debugged.