We had a situation where MacGDBp would hit a breakpoint but couldn't display the related file, even though the file was accessible for MacGDBp. The problem was traced to a faulty PHP CLI install.

MacGDBp uses the PHP CLI binary for syntax highlighting (clever! :) ), which is fine, except it doesn't detect when the PHP CLI is available but doesn't work.

MacGDBp should check the exit code for the PHP binary, to see if highlighting actually worked and give a proper error message if it didn't work.

What was wrong with the PHP CLI install? And what did MacGDBp do with the bad output? Did it crash? Finally, if I posted a beta build would you be able to test and see if you can replicate the issue?

I think one of the PHP extensions was dynamically compiled against a particular library that resulted in unresolved references. MacGDBp silently failed, not showing anything in the File pane.

Perhaps you can reproduce it by trying to load a PHP extension which was compiled for a different PHP version than the one you're using.

Thank you for your bug report. This issue has been closed and fixed in git. This change will be available in a future release, but you can download the change at any time from the git repository, found at http://www.bluestatic.org/git/.