Debugging fails on a project by project basis

Posted December 28th, 2006 by ederek

There are a lot of postings about outright failure of the debugger to recognize a breakpoint. My symptoms are perhaps more elusive since for me, some projects load and debug without any problem, and others do not.

I have compared the .sln and .phpproj files, as well as the .httpd.conf files for working and non-working projects and do not find any indicator for why one works and another does not.

In the DBGListener log, a working project will show the 'client connected' message and hold at that point. A non-working project will show the 'client connected' message immediately followed by the 'client disconnected' message.

I have tried creating brand new projects with a single .php file containing only phpinfo(); and it does not break, but then I can open a pre-existing project with hundreds of files and it will break at any and all breakpoints throughout.

Any insight, comments or suggestions are appreciated.

‹ Struggling with Debugger from Page to Page Debug crashes under vs2005 on x64 ›

Comments

    DbgView

    On January 1st, 2007 juanc said:

    Try installing DebugView and see the traces for more information:

    http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx

    It should give us more information about what the problem is.

    DbgView Result files

    On January 2nd, 2007 ederek said:

    Thanks for the suggestion.

    The following links are to the two log files generated by the two projects: one works and one does not.

    Project A: the one that will NOT stop at breakpoints: http://www.edivise.com/tmp/daybreak-debug2007-01-02.log.txt

    Project B: the one that DOES stop at breakpoints:
    http://www.edivise.com/tmp/fod-debug2007-01-02.log.txt

    It is pretty evident that the debugger is not attaching properly. It is less evident as to why.

    Thanks for your help.
    Derek