Crash when debugging with XDebug in builtin mode (VS.PHP for VS 2008)

Project:VS.Php for Visual Studio 2008
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active
Description

Whenever debugging session "supposed" to hit a breakpoint there is a crash with:

"AppName: vsphp_dbg.exe AppVer: 2.2.1.3208 ModName: msvcr90.dll ModVer: 9.0.21022.8"

This is for PHP4 and PHP5. Debugging with old DBG method works fine. This happens for both XP and Vista64.

If no breakpoints specified, all works fine and phpinfo reports successful loading of xdebug.

It was working fine a while back (not sure exactly, probably about a month) but after installing one of the development builds, xdebug stopped working.

Updates

#1 submitted by webmaster on Thu, 2008-03-13 15:45

What version of VS.Php are you using? What OS are you using? Could you get a memory dump for further analysis?

Comments

    further info

    On March 14th, 2008 kolba said:

    after trying out a few dev. builds I managed to pinpoint the problem to build 2.4.2.4431. i.e. build 2.4.2.4428 works fine, but starting from build 2.4.2.4431 the problem exists up to the latest build 2.4.3.4486

    I'm running WinXP SP2 now, but the problem happens on Vista64 too.

    If you still require a memory dump, I could provide it if I find out how to do it properly for you.

    thanks.

    Kolba, Excellent work

    On March 14th, 2008 webmaster said:

    Kolba,

    Excellent work finding out the build that cause the issue.

    From looking at the changes made, nothing jumps right out as the problem but interestingly enough those changes were made to prevent some crashes! How ironic :)

    Getting a memory dump for vsphp_dbg would be really useful but it is a little bit tricky. You have to use the remote debugger to attach to the process because it is already been debugged. You use a tool called msvsmon.

    After you attach to it you can get the memory dump as you typically do from the debug menu->save mem dump.

    I'm going to look at some code here because I have an idea what could be wrong.

    If I find a solution, I'll send you a private for testing.

    Again, excellent investigative work. It really helped!

    Thanks

    BTW, are you using XDebug or

    On March 14th, 2008 webmaster said:

    BTW, are you using XDebug or DBG?