Hello, I'm using your product in 10.5.3 and I'm having trouble using the GUI for more than one request. Here's what happens: I connect an begin debugging using ?XDEBUG_SESSION_START=1 in the Get, hit a breakpoint, inspect a variable and then press the play button. From then on, the GUI shows 'stopping' in the status tray, but control is never returned to the browser. Additionally, subsequent requests fail to renew the GUI. Must I restart the application for each debugging session?

Could you please attach the crash logs to the bug report? On Leopard they're located in ~/Library/Logs/CrashReporter/. You can attach them to the bug report. Also, can you post the settings for xdebug you have in php.ini? I take it you don't have remote_autostart set? If not, can you try turning remote_autostart on and seeing if you still have the problem?

I've gotten another report of the "Stopping" status -- I have not experienced it, so I'm in flying in the dark a little right now. The status *should* be "Stopped" when you hit the play button, so hopefully crash logs will reveal some information.

As Requested...

Again... More crash reporting.

My php.ini settings:
[xdebug]
zend_extension=/Applications/MAMP/bin/php5/lib/php/extensions/no-debug-non-zts-20050922/xdebug.so
xdebug.remote_enable=1
xdebug.remote_host=localhost
xdebug.remote_port=9000
xdebug.remote_autostart=1

PS: I'm using MAMP, so I had to turn off the zen optimizer in order to run the extension.

I still have not been able to confirm this bug myself, but my initial suspicion as to what caused it was wrong. I now have no idea what would be causing this bug :-). It looks like it could be due to using Obj-C garbage collection, so please try this beta version to see if it fixes the issue.

I'm also experiencing the same bug. I downloaded the beta attached to this report and it did not fix the problem. I also have an additional problem in that the exact same behavior occurs when I step through a script and reach the end of the script. The debugger window displays 'stopping' and just hangs.

If I close the debugger window without closing MacGDBp, the script will then continue to execute. However, MacGDBp will not respond until I close it out and restart it. So I pretty much have to run the web application till just before it loads the script I want to debug, fire up MacGDBp, and then I can step through the script until I reach the end of the script at which point, the debugger window displays 'stopping' and the script execution hangs until I close the debugger window.

Also running 10.5.3
MAMP
PHP 5.2.3

If you're experiencing crashes with 1.0.1, please post those as well. If you open up the crash report in TextEdit (or something similar) the version should be: "Version: 1.0.1 (20080618.493439b)" and not "1.0 (20080617.6502571)".

I've added the crash report for 1.0.1... I've discovered a new bug in this version. The application exits when I try to add a breakpoint.

Alright, that's a better crash! Is the crash reproducible at all times, when debugging all scripts, and via a path of specific steps? If so, can you please tell me what script(s) you're trying and the steps you follow to get it to crash?

It happens on all scripts, I've tried the mamp start page, the php info page, phpadmin, and a simple "hello world" script I wrote to test it as well as various php apps I have written in the past.

I fire up GDBp, open a page, it pauses. I click play and the debugger window displays "stopping" and just hangs till I close it. Or, if I start stepping through the code, as soon as it finishes and tries to render output to the browser, the debugger window displays "stopping" and hangs till I close it. Once I close GDBp, the script output is renedered in the browser window.

If I fire up GDBp and want to set a breakpoint, I select the script (any script) I want to set the breakpoint in. It loads the script fine, but as soon as I click on a line to set a breakpoint, GDBp crashes. This did not happen vith version 1.0....

Thanks so much to all of you for giving me information. I can now reproduce both of these problems and will start looking for a fix. Are all of you using MAMP? If so, I think that may actually be the problem; maybe it's an extension mismatch.

I've attached a new beta build that will fix the crash. I'm still working on the "Stopping" issue, however.

And a final build. This should fix both issues. If it does, I'll go ahead and release this.

The play button works now, I don't have time to test breakpoints right now, but I will later. I'm only using MAMP because that is what you guys recommend...

http://www.bluestatic.org/software/macgdbp/help.php

Alright, thanks unclejoe. I know I recommend MAMP -- it may just be some configuration+extension that causes it to go to "Stopping" rather than "Stopped." But it should be fixed now!

Ok, I just tested and breakpoints are now working as well. Thank you so much for an excellent tool.

Hey! That's better! We're getting closer, the debugging actually works, which is a vast improvement. You're doing a great job. However, after pressing play to continue debugging, the control returns to the page, but the debugger continues to say 'stopping' instead of what I imagine should say 'stopped'. In order to debug my next script, I must press the power button (top right green button) to power on/off. I assume you want the debugger to move from 'stopping' to 'stopped', and await the next script.

Also, you've got what appears to be a fencepost error on your breakpoint screen. For example, if I want to set a breakpoint on line 66, I have to click line 67.

Keep up the good work. I'll be reviewing your product on ParticleTree this week, bugs and all. I'm happy to have a debugger and I'll write favorably about your product. I'll work with you to squash as many bugs as possible between now and then.

Thanks!
Tim

I've made it so that "stopping" will no longer be displayed, but "stopped" will. And I'm now closing this bug because it seems to be resolved. I'll track the fencepost clicking bug at bug 128.