From: dimm AT vnet DOT ibm DOT com Subject: Re: Use GDB for not GCC's exes 23 Oct 1996 11:35:00 -0700 Sender: daemon AT cygnus DOT com Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <326E04C5.794B.cygnus.gnu-win32@vnet.ibm.com> References: <326369A2 DOT 960 DOT cygnus DOT gnu-win32 AT missinglink DOT co DOT il> <326C54FB DOT 46D6 DOT cygnus DOT gnu-win32 AT missinglink DOT co DOT il> <326DCB1D DOT 6241 AT missinglink DOT co DOT il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (X11; I; AIX 2) Original-To: gnu-win32 AT cygnus DOT com Original-Cc: Michael Snyder Original-Sender: owner-gnu-win32 AT cygnus DOT com > Michael Snyder wrote: > > > > be a highly desireable secondary goal. Whether that will happen is at > > least in part dependant on who would want it and how badly. Does > > anybody else think that using gdb to debug code compiled with > > MicroSoft compilers is an important feature? Oh, yeah, but alternatively you could make gcc generate debugging information in format understandable by MS debugger, say the one that is in MS Dev. Studio. While gdb doesn't work on PPC/NT, cygwin32 is pretty much useless on PPC/NT too, as a developer's environment... Dmitri Makarov. dimm AT vnet DOT ibm DOT com - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".