RE: Codeview debugging info

[Stephan Mueller <smueller at microsoft dot com>]

Actually, NT will bring up the debugger registered in the registry.  On
a 32-bit system, it's unlikely that is ever CodeView.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger is the
debugger-command-with-arguments to launch when you select Debug from the
Task Manager (or Just In Time debugging at a GP fault).  You can change
this value.

On my machine, the value is
	d:\msdev\bin\msdev.exe -p %ld -e %ld

I just replaced it temporarily with a batch file that simply prints out
the two %ld values.  It appears that the presence of the -p %ld -e %ld
parameters is ignored, and "-p <processid>" is always added, at least
when using Debug from Task Manager.

So if you hack your debugger to take -p and a process id if it doesn't
already, you may be able to get useful results by playing with this
registry key.

stephan(not speaking in any official capacity, just for myself.  Hacking
your registry is dangerous.  Do so at your own risk.);

> -----Original Message-----
> From:	Geoffrey Noer [SMTP:noer@cygnus.com]
> Sent:	Friday, May 02, 1997 1:34 AM
> To:	jp@nuancecom.com
> Cc:	noer@cygnus.com; gnu-win32@cygnus.com
> Subject:	Re: Codeview debugging info
> 
> >   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 not currently any plans to do this...
> 
> -- 
> Geoffrey Noer
> noer@cygnus.com
> -
> For help on using this list (especially unsubscribing), send a message
> to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".