Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12689 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93985 invoked by uid 1010); 9 Sep 2004 19:05:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 86883 invoked from network); 9 Sep 2004 19:03:28 -0000 Received: from unknown (HELO duplo.phpwebhosting.com) (66.132.170.61) by pb1.pair.com with SMTP; 9 Sep 2004 19:03:28 -0000 Received: (qmail 8175 invoked from network); 9 Sep 2004 19:03:27 -0000 Received: from unknown (HELO ?10.0.2.78?) (65.200.4.130) by duplo2.phpwebhosting.com with SMTP; 9 Sep 2004 19:03:27 -0000 Message-ID: <4140A908.9000500@ganx4.com> Date: Thu, 09 Sep 2004 12:03:36 -0700 User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wez Furlong CC: internals@lists.php.net References: <20040905193319.91641.qmail@pb1.pair.com> <20040905211921.39505.qmail@pb1.pair.com> <20040905223229.41761.qmail@pb1.pair.com> <5.1.0.14.2.20040906231133.06501800@localhost> <20040907091235.5283.qmail@pb1.pair.com> <413E02BF.4080604@ganx4.com> <4e89b42604090911107681e23c@mail.gmail.com> In-Reply-To: <4e89b42604090911107681e23c@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Really odd PHP problem... different platform From: dietrich@ganx4.com (Dietrich Ayala) excellent tips, thx dan and wez. do i need to do add any special options to the debug build configuration to generate the debug symbols? also, what is the release_tsdbg build configuration? a release build w/ debug symbols? i'll check out the minidump idea. that'd be ideal, as the client is remote and won't allow remote access to their box. thanks, dietrich Wez Furlong wrote: > 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 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 >> >> > > >