Re: [INTERNALS-WIN] Crash dump reports

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" >> 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