Trivial :-)
First, it's easiest to set up the Debug parameters with the 'target'
apache executable (c:\apache2\bin\apache.exe or whatnot), assure the
path is correct (c:\apache2) and use "-X" for the program arguments.
This assures the system will not launch children, so debugging stuff
in apr, protocols, modules etc is much simpler.
If you are trying to validate the mpm parent/child environment, it
gets a bit less trivial (but not much). If you need to jump in very
early, set up DebugBreak() calls where you like them to catch the
child in action. Otherwise use the task list to determine which
apache process has 50+ threads (as opposed to < 5 threads) and use
the IDE's attach-to-process feature. If you are debugging the service,
you will need to select 'show system processes' to even find the apache
child process.
Bill
----- Original Message -----
From: "Ian Holsman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 08, 2001 11:22 AM
Subject: Win32: Debugging Apache 2.0 with VS GUI
> hi.
> I was just wondering how to go about debugging apache2
> inside of Visual C++'s IDE. I set a breakpoint but it never
> gets hit.
>
> any pointers???
>
> also if anyone has tips about using the profiler in win32.
>
> Thanks
>
> Ian
>
