I can't see the full call stack. Only the "top" item is shown, and it's got "..." so it's not even that useful...

Can I have a screen shot? Are you doing remote debugging or local debugging? Finally, try a different web app to debug and see if it occurs.

I noticed that it works if I step into functions, but it doesn't figure out the "current" call stack when I step over the xdebug_break().

I also tried it using a breakpoint and it didn't work that way either...

Hope that helps,
Alan

In searching for the cause of this bug, I ran into a significant issue with the way the run/continue functionality is implemented. I have fixed that problem in this build. Since I cannot replicate your report myself, I'm not sure this will fix it. But, I can imagine that the issues are related.

Ok, that actually did fix the stack trace, but it broke debugging :(

Step Over / Step Into no longer work. When you press them, the stack trace updates but not the code view. The "current line being executed" indicator just stays on the xdebug_break() line and never advances. I think it is actually stepping, it just isn't updating the code view area.

I've attached a new beta build that may fix the problem. Please test it and let me know if it works or not.

Same problem. Call stack is correct; stepping doesn't advance "line" pointer.

Is the code pane advancing correctly? Can you check /Applications/Console.app when you're running MacGDBp and see if any errors from the program are outputted?

Nothing is showing in console.log, sorry.

I've attached a new build, which is the 1.3 release candidate. Can you see if the issue is now resolved? I just want to confirm that the issue has changed, right? The call stack is now OK, but the code display isn't?

1. You are correct; the call stack now works, if you want to close out this bug.
2. Also correct, the code display doesn't update (really it's just the "PC" pointer). Some additional notes on this:
- The PC works correctly if I step from the "stop at first line" built-in breakpoint (which btw there should be a preference to skip breaking at first line, it's annoying!)
- The code will stop at an xdebug_break(), but not at a "breakpoint" set in the gutter of MacGDBP.
- The code won't step correctly when stopped at xdebug_break().

I've attached another build. I'm pretty confident this should fix the issue.

That fixed it!

Where should I make feature requests? There are a few little things like:
- After you hit "play" the "pink highlighting line" should disappear. The fact that it still shows up like it's stopped is a little confusing.
- It'd be nice to have a preference to "always listen for debugger connections". It's annoying to have to always "turn on" the debugger for each run. XDebug already has much more convenient ways to toggle debugging (cookies, request vars, and XDebug Helper firefox plugin).

Alan

I'm glad that did it! You can submit feature requests in this bug tracker. Simply set the severity to be "Enhancement". Thanks.

--------------- AUTOMATIC RESPONSE ---------------
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/.