I'd recommend the Microsoft "Debugging Tools for Windows" to be able to do very similar things to gdb under windows; it's free, not as bloated as VC++/VS.Net IDE debugger and comes in console and GUI flavours.
Caveat emptor: - you need to understand how to debug - you want a debug build of php with symbols to do much with it Also, it should be possible (although I've never found out exactly how) to have the OS/Dr. Watson produce a minidump which you can then post-mortem backtrace with these tools on a developers box (similar to gdb'ing a core file on unix). The advantage of this is that your client wouldn't need to install the debugger and operate it themselves. Hope that helps.... (and if you find out about the minidump thing, please share the knowledge ;-) --Wez. On Tue, 07 Sep 2004 11:49:35 -0700, Dietrich Ayala <[EMAIL PROTECTED]> wrote: > A large telco client of ours is having problems that match Russ' problem > almost exactly... except on Win2k. > > Does anyone have pointers to *windows* tools to achieve the kind of > debugging/tracing described below? > > Rasmus Lerdorf wrote: > > On Tue, 7 Sep 2004, Russ Garrett wrote: > > > >>I can watch them for hours in the apache mod_status view, and they'll > >>show the same last request. They won't respond to a kill -15, I have to > >>kill -9 them. Strace reports they're doing absolutely nothing. > > > > > > Could you use 'gcore' to drop a core from one of these spinning processes > > and get a backtrace, or simply attach gdb to one of them and see if you > > can get a backtrace. Chances are it's off in the middle of nowhere, but > > by poking around a bit and looking at 'ap_request' and walking through > > 'ap_request->headers_in' you should be able to get an idea of the exact > > request that caused it to go nuts. > > > > -Rasmus > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
