On Thu, Mar 25, 2010 at 8:49 AM, Thomas Hruska <thru...@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
