If I ctrl-c a php script while it is on hold in MacGDBp, it crashes as soon as I continue debugging ("continue" or "step over", "out" or "in").

Expectation: MacGDBp closes current connection.

Suggestion: Make Reset button also active when connected. It closes the connection on click.

I think this has been fixed indirectly via some refactoring and cleanup in 1.4. Please test if this is true with the attached beta build.

Also the 1.4 beta build exits when trying to resume debugging (to exit) an aborted PHP script. There is no feedback, not even the Mac OS "The Application was unexpectedly terminated" dialog.
Mac OS 10.5.7 with MacGDBp 1.3.0.25 and 1.4.0.31

Then I have yet to be able to repro locally. Here's the test script I've been using. Can you try it with build 31 and see if it occurs? Also, please open /Applications/Utilities/Console.app and see if there's any output from MacGDBp after the crash. There may also be a crash log in ~/Library/Logs/CrashReporter/MacGDBp*.

The attached beta build again has the UTF-8 corruption problem that was fixed in 1.3.0.25

Yes, I figured that'd be a possibility. Either way, I'm rewriting the networking stuff (again!) and hopefully that will fix this and a myriad of other issues. That will come in 1.3.1.

Newest build crashes also with test.php.

Console output:
24.07.09 18:28:09 com.apple.launchd[235] ([0x0-0x126126].org.bluestatic.macgdbp[36883]) Exited abnormally: Broken pipe

No crash report written.

To reproduce locally:
1. open MacGDBp
2. $ php test.php
3. ctrl-c (in shell)

On "continue" MacGDBp crashes.

I really like the new "automatic reconnect" feature!

Is this still an issue for you in 1.4.1.?

Yes, it is fixed now. If you ctrl+c in the terminal, MacGDBp waits in break mode. Clicking on continue or other buttons have no effect and it can be set in stop mode with the stop button. Thanks!

Excellent; glad to hear it.