Re: [INTERNALS-WIN] Crash dump reports
| From: | Pierre Joye | Date: | Mon, 23 May 2011 19:07:58 +0000 |
| Subject: | Re: [INTERNALS-WIN] Crash dump reports | ||
| References: | 1 2 3 4 5 | Groups: | php.internals.win |
| Request: | Send a blank email to internals-win+get-789@lists.php.net to get a copy of this message | ||
adding Hannes to the list, he knows these issues well, no matter the platforms
On Mon, May 23, 2011 at 2:39 PM, Richard Quadling <rquadling@gmail.com> wrote:
> On 23 May 2011 12:54, Pierre Joye <pierre.php@gmail.com> wrote:
>> not easily right now. But you can get it to save the dump somewhere,
>> then you can generate a bactrace using this dump. That's why I pointed
>> you to this howto.
>>
>> On Mon, May 23, 2011 at 1:51 PM, Richard Quadling <rquadling@gmail.com> wrote:
>>> On 23 May 2011 12:42, Pierre Joye <pierre.php@gmail.com> wrote:
>>>> hi,
>>>>
>>>> See the "how to generate a backtrace"
>>>> â
>>>> ¾DY‘ñøy<\inò³Úhttp://bugs.php.net/bugs-generating-backtrace-win32.php
>>>>
>>>> On Mon, May 23, 2011 at 1:15 PM, Richard Quadling <rquadling@gmail.com>
>>>> wrote:
>>>>> Hi.
>>>>>
>>>>> Currently, I'm getting a crash when I run PhD using my build (as well
>>>>> as the build on the server that builds the Windows CHM files).
>>>>>
>>>>> It generates a Dr Watson log and I'm pushing it off to MS.
>>>>>
>>>>> Where do they go?
>>>>>
>>>>> Can they be retrieved/analysed?
>>>>>
>>>>> Is there anything being done with these reports?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Richard.
>>>>>
>>>>> --
>>>>> Richard Quadling
>>>>> Twitter : EE : Zend : PHPDoc
>>>>> @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea
>>>>>
>>>>> --
>>>>> Windows Internals Mailing List (http://www.php.net/)
>>>>> To unsubscribe, visit:
>>>>> http://www.php.net/unsub.php
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Pierre
>>>>
>>>> @pierrejoye | http://blog.thepimp.net |
>>>> http://www.libgd.org
>>>>
>>>
>>> The server in question only reports the crash after a logout/login.
>>>
>>> And only for 1 of the languages that crashes (es or fa - will need to
>>> check locally).
>>>
>>> But with the reports being sent to MS, isn't there a way to collate
>>> these and get them part of the debugging process?
>>>
>>>
>>>
>>> --
>>> Richard Quadling
>>> Twitter : EE : Zend : PHPDoc
>>> @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea
>>>
>>
>>
>>
>> --
>> Pierre
>>
>> @pierrejoye | http://blog.thepimp.net |
>> http://www.libgd.org
>>
>
> The backtrace ...
>
> PHP5!XMLSTREQUAL+20
> In php__PID__6948__Date__05_23_2011__Time_01_06_23PM__684__Second_Chance_Exception_C0000005.dmp
> the assembly instruction at php5!xmlStrEqual+20 in C:\PHP5\php5.dll
> from The PHP Group has caused an access violation exception
> (0xC0000005) when trying to read from memory location 0x73746e65 on
> thread 0
>
> Whereas the start of the trace has source code paths and line numbers,
> the later entries don't. And as xmlStrEqual is in libxml, it suggests
> an error there.
>
> I'm using libxml-2.7.7-vc9-x86.zip.
>
> There is a 2.7.8 branch on
> http://git.gnome.org/browse/libxml2/tag/?id=v2.7.8, and
> http://xmlsoft.org/news.html shows a new release, but no win32
> binaries on http://xmlsoft.org/sources/win32/ or
> http://www.zlatkovic.com/libxml.en.html or
> http://www.zlatkovic.com/libxml.en.html
>
> So. I wonder just how hard it is to build?
>
> Or do you need to do work to the code to make it compatible with PHP?
>
> Richard.
>
> --
> Richard Quadling
> Twitter : EE : Zend : PHPDoc
> @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea
>
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org