Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47593
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.216 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=YKqo8u/5/udtQZmwMfYn1yVCB0CFaEqnlcCUm7fFwdoKwmU7ZRs8gV9Rp7e0rBVmXH
         y0Z3U2yZWveP7WEkCZrF7Vb1EuzZucukHKz8bcv8UNrngT9vsEcTkmLbaeoscFVJM4L8
         1SUGX8+TH77PAMjJagMCSkecLilOztKICglAI=
MIME-Version: 1.0
In-Reply-To: <4BAB15A6.2010206@cubiclesoft.com>
References: <4BAB0190.8090103@cubiclesoft.com>
	 <b54d0abe1003242338t2e079578l68530c644ff56135@mail.gmail.com>
	 <4BAB15A6.2010206@cubiclesoft.com>
Date: Thu, 25 Mar 2010 09:51:41 +0100
Message-ID: <b54d0abe1003250151y5fdb6b97n876c1bdaaa354a70@mail.gmail.com>
To: Thomas Hruska <thruska@cubiclesoft.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=00032555316ad6075904829c279e
Subject: Re: [PHP-DEV] How to trace a crash bug?
From: tyra3l@gmail.com (Ferenc Kovacs)

--00032555316ad6075904829c279e
Content-Type: text/plain; charset=UTF-8

On Thu, Mar 25, 2010 at 8:49 AM, Thomas Hruska <thruska@cubiclesoft.com>wrote:

> Ferenc Kovacs wrote:
>
>> apache version?
>>
>
> If you read the message, you would see "Apache 2.2.13".
>
>
> I mean where did you get it? You build it for yourself, you downloaded from
apache.org, or from different source?

>
>  php version? thread safe, or nts?
>>
>
> If you read the message, you would see "PHP 5.2.13".  I didn't mention
> thread safe.  Sorry.  Forgot about that

You build it yourself?  You downloaded from windows.php.net?

> .
>
>
>
>  does it crash with a hello world script, or only with your complex script.
>> if its crash only with your script, then we cant help without a testcase.
>>
>
> That is what I am trying to do:  Come up with either a simple test case OR
> pinpoint the crash in the C code.  The simple test case route wasn't
> working, so I'm left with tracing the code.  Hence my query.
>
> to debug with visual studio:
http://bugs.php.net/bugs-generating-backtrace-win32.php

>
>
>  btw: I think you've chosen the wrong mailing list with your problem, the
>> internals mailing list is for the php developers who write php engine in
>> C,
>> not for developers who writes php applications.
>>
>
> I'm pretty sure I'm on the right list.  I know C/C++ and want to hook into
> the PHP source with a C debugger (VS IDE, preferably).  In other words, I'm
> going to be digging around in the engine to find this problem.  Plus, this
> will give me a good look at the guts of PHP.
>
>
>
>  ps: if you found a bug, open a ticket in the bugtracker.
>>
>
> Will do after I've got a reasonable test case and/or patch to work with.
>  Simply saying "PHP crashes with complex code" isn't helpful to anyone.  I
> was basically after a general guide for getting a Debug build that I can
> hook into with the VS debugger and stop on crash bugs from within the Apache
> module.
>
to build on your own:
http://wiki.php.net/internals/windows/stepbystepbuild

> .
>
Oh well.  I'll try to build and will get back to you.  I can't do anything
> else on this project until I figure out this bug.  I probably should grab
> the latest snapshot just in case...
>
The trunk was branched not long ago from the 5.3 branch, so I think there is
little chance that your problem is fixed there, so you can use the stable
debug build if its easier for you.

Tyrael

--00032555316ad6075904829c279e--