|
From: Alfred P. R. <al...@ya...> - 2006-01-18 01:13:20
|
Why invoke Insight inside Dev-C++? In my experience, all bug issues related to debugging anything except rudimentary programs occurred while debugging from inside Dev-C++. The current version of Insight is fairly stout, BTW. Vale Group <val...@at...> wrote: Thierry Pierron wrote: > I'm using Dev-Cpp (4.9.9.2) for a while now, and I find it good, > though it remains some details that annoy me : > 2. The console output of gdb is nearly unusable. To get a useable debugger I invoke Insight as a DEV-C++ tool: Program: C:\cygwin\bin\insight.exe Working Directory: C:\cygwin\bin\ Parameters: "" Note: Enclose the bracketed EXENAME in quotation marks so that program names with embedded spaces will be called correctly. I think the Dev-C++ project is dormant although I still use it. Josh mentioned Code::Blocks which is the heir apparent to Dev-C++. Check this list's archive for a discussion of the topic a few months ago. -- Chuck Alfred P. Reaud |