From:	dbakin AT intrinsa DOT com (Dave Bakin)
Subject:	Re: Codeview debugging info
2 May 1997 19:11:20 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<2.2.32.19970502142515.00acb61c.cygnus.gnu-win32@intrinsa.com>
Mime-Version:	1.0
X-Sender:	dbakin AT intrinsa DOT com
X-Mailer:	Windows Eudora Pro Version 2.2 (32)
Original-To:	JP Shipherd <jp AT nuancecom DOT com>
Original-Cc:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Although the system will automatically bring up one debugger, you get to
pick the debugger.  On Windows 95 look in win.ini for [aedebug].  On Windows
NT look in the registry for an aedebug key.  Look at the knowledge base
articles at http://www.microsoft.com/kb/articles/q103/8/61.htm and
http://www.microsoft.com/kb/articles/q138/7/86.htm.  So if you want to
always launch gdb, try setting up the system for it and see if it works.
(Let us know!)

-- Dave

At 05:59 PM 5/1/97 -0700, you wrote:
>Hello,
>
>  I'm wondering in Cygnus ever plans to offer an option to generate
>Codeview debugging info (instead of stabs).  Windows NT Task Manager lets
>you click on any process and debug it, however it only brings up codeview
>(if it is loaded on your system).
>
>  There are also a variety of products (BoundChecker, etc), that work on
>code with Codeview debugging info.  The Watcom compiler provides this
>option and it really lets me choose both a superior compiler and my choice
>of popular debugging tools.
>
>Thanks,
>--jp
>
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -