From: Oscar F. <of...@wa...> - 2002-09-11 20:17:43
|
"Al Stevens" <al...@al...> writes: [snip] > It has been mentioned here that the MinGW gdb is an old version. Maybe a > newer version would not have this problem. I downloaded the cygwin debugger, > which some folks here have mentioned, only to find that it is not a command > line debugger at all, but a GUI application. Bummer. That's Insight. It is a GUI with gdb embedded. As Greg suggested, the -nw switch cures this. But keep reading. > Before I immerse myself in the daunting task of porting gdb from source to > something that works in the IDE environment, I will ask here: > > <simple question> > Is there somewhere I can download a newer command line gdb that is built to > work with either cygwin1.dll or as a MinGW executable? > </simple question> Well, I'm using the 5.2.1 version built from sources under Cygwin. This is the real 'gdb', not Insight, so no -nw switch needed. > My google search has not turned one up. > > I fear that the problem is the platform api and not gdb itself. As for the console problem is related, I think so. Maybe an investigation about the different Win32 APIs for launching applications could yield some interesting stuff. [snip] > I have a number of older gdbs that I will be trying today, but I'd prefer to > have something that knows more about the debug info (stabs) that support > contemporary C++. As others said on this list just a few days ago and my experience confirms, gdb 5.1.1 doesn't work well with C++. You really want to use the latest one. [snip] -- Oscar |