Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23019 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10004 invoked by uid 1010); 29 Apr 2006 05:02:29 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 9989 invoked from network); 29 Apr 2006 05:02:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Apr 2006 05:02:29 -0000 X-PHP-List-Original-Sender: wrowe@rowe-clan.net X-Host-Fingerprint: 207.155.252.112 leander.cnchost.com Solaris 9 Received: from ([207.155.252.112:64749] helo=leander.cnchost.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 3C/83-18514-463F2544 for ; Sat, 29 Apr 2006 01:02:28 -0400 Received: from [192.168.0.21] (c-24-15-193-17.hsd1.il.comcast.net [24.15.193.17]) by leander.cnchost.com (ConcentricHost(2.54) Relay) with ESMTP id 886CC401C; Sat, 29 Apr 2006 01:02:20 -0400 (EDT) Message-ID: <4452F35B.8050807@rowe-clan.net> Date: Sat, 29 Apr 2006 00:02:19 -0500 User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hannes Magnusson CC: Sharad Gupta , internals@lists.php.net References: <82bc920f0604281846p2ebbd32ao8593f00c3d5c8638@mail.gmail.com> <7f3ed2c30604281908t31a45e05x5384aad093f5b021@mail.gmail.com> In-Reply-To: <7f3ed2c30604281908t31a45e05x5384aad093f5b021@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Help with generating a stack trace on IIS6 From: wrowe@rowe-clan.net ("William A. Rowe, Jr.") Hannes Magnusson wrote: > Hi Sharad > >> I would appreciate if anyone can help me in finding out how to obtain >> extra >> information from php ... I am not able to find a debug pack for PHP 4 >> .... The sad bit is, it's totally unnecessary to have a specific debug build, but the maintainers have never taken advantage of the fact. Leave /O options alone in the release build (optimize to your hearts' content), leave /MD for the run time, but compile with the /Zi flag (ensuring the sources don't clash with the output binary name, or else use /Fd"othername" to compile the sources with a different .pdb filename to avoid a collision), and finally link /debug /opt:ref. The result is the -same- .dll or .exe as the original release style, but an -external- .pdb matching the binary - which Dr. Watson or any other windows debugger can use and spit out backtraces. Windows Apache HTTP Server releases offer this; the corresponding .pdb's are zipped up in their very own package. Normally they don't help a user. But if the user is crashing, unzipping the .pdb files that correspond to their release provides all the backtrace info required. In fact, with the binaries + pdb's - the user.dmp crash file can be ripped open on a dev box which has the appropriate debugging tools, just like using an non-stripped unix binary with gdb. Bill