Hello, guest. We have noticed that you are not registered at this bug tracker. Your experience will be greatly enhanced if you log in. To do so, you first must register by clicking on the Register tab at the top. If you are already registered, you can login at the Login tab.
Syndicate Syndicate Listing Display Search Login/Register
Bug Id ?
Reporter ?
Alan Pinstein
MacGDBp / 1.2.1
Status ?
Severity ?
Duplicate Of ?
- none -
Fixed in Revision ?
Mstone ?
Summary ?
Call stack not displayed.
Report Time ?
March 17, 2009 12:30 AM
Assignment ?
Resolution ?
Priority ?
Dependencies ?
- none -
Mstone (old) ?

Picture 1.png Screenshot of call-stack bug.
MacGDB-10.zip Unlikely, but possible fix
MacGDBp-12.zip New beta build
For: 0 (0%)
Against: 0 (0%)
Total: 0

March 17, 2009 12:30 AM Alan Pinstein
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...

March 23, 2009 07:07 PM Robert
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.

March 23, 2009 07:28 PM Alan Pinstein
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,

April 10, 2009 03:05 AM Robert
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.

April 11, 2009 03:47 AM Alan Pinstein
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.

On May 10, 2009 02:13 PM, Robert changed:
May 10, 2009 02:14 PM Robert
I've attached a new beta build that may fix the problem. Please test it and let me know if it works or not.

May 11, 2009 01:04 AM Alan Pinstein
Same problem. Call stack is correct; stepping doesn't advance "line" pointer.

May 12, 2009 04:24 AM Robert
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?

May 16, 2009 05:19 PM Alan Pinstein
Nothing is showing in console.log, sorry.

On May 16, 2009 07:17 PM, Robert changed:
May 16, 2009 07:18 PM Robert
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?

May 16, 2009 07:29 PM Alan Pinstein
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().

On May 17, 2009 03:58 AM, Robert changed:
May 17, 2009 03:59 AM Robert
I've attached another build. I'm pretty confident this should fix the issue.

May 17, 2009 03:06 PM Alan Pinstein
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).


May 17, 2009 03:26 PM Robert
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/.

On May 17, 2009 03:26 PM, Robert changed: