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 ?
Product/Version ?
MacGDBp / 1.3.1
Status ?
Severity ?
Duplicate Of ?
- none -
Fixed in Revision ?
Mstone ?
Summary ?
Inspector not showing anything
Report Time ?
February 7, 2010 11:55 AM
Assignment ?
Resolution ?
Priority ?
Dependencies ?
- none -
Mstone (old) ?

For: 0 (0%)
Against: 0 (0%)
Total: 0

February 7, 2010 11:55 AM Tobias
I've got MacGDB stopping on breakpoints. But for all the variables the value shows as empty. Also, I can pop up the dark inspector window.

The local variables are all "unintialized", which is simply not correct. Any hint what I might have configured wrong?

I'm using PHP 5.3 (the one bundled with Snow Leopard), xdebug 2.0.5 and MacGDBp Version 1.3.1 (34).

February 7, 2010 02:18 PM Robert
Re TransportDebug not working: Are you looking at the right log in Console.app? Click 'Show Log List' if it's not already open and choose 'All Messages'.

Your phpinfo.txt looks identical to mine for the Xdebug configuration.

February 7, 2010 02:26 PM Tobias
I'm sure yes, sorry ;)

The only "relevant" entry is »07.02.10 16:23:17 Firewall[25518] MacGDBp is listening from proto=6«. Nothing else.

As addition I've search the log for MacGDBp items of all time and attached it as a second attachment. Maybe it helps.

February 7, 2010 02:27 PM Robert
Does the rest of MacGDBp work (like the source viewer and the stack display)? Can you try disabling the firewall?

February 7, 2010 02:29 PM Tobias
Yes, souce view and stack display works fine.

Firewall is no problem, I allowed MacGDBp to accept connections. Anyhow I already disabled it and got the same result.

It looks like this is only the case with local stacks. Global variables always work, local ones never.

February 7, 2010 02:31 PM Robert
That's bizarre. It looks like it may be trying to error out, but is failing. This could be related the the crash. Can you upload the crash report here? /Users/tobias/Library/Logs/DiagnosticReports/MacGDBp_2010-02-07-141118_Beaver.crash

February 7, 2010 02:33 PM Tobias

February 7, 2010 02:47 PM Robert
Thanks. I've fixed one of the bugs that was revealed from your Console output. Please try build 37, which I uploaded here. It should now properly report any error messages in red text in the lower corner. Also, under what circumstances did those crashes occur?

February 7, 2010 03:07 PM Tobias
I'm sorry to tell, but the "unintialized" issue is still valid. I've also attached a screenshot, maybe it helps in any way … ;o)

Regarding the crash I'm not exactly sure. I guess it was a case where I canceled the request inside the browser, and tried to continue debugging (which of course was not what I wanted, just pressed the wrong button ;o)

February 7, 2010 03:08 PM Tobias
Also, can you please delete Current Issues.mindnode.zip from this report. It was not supposed to be uploaded ;o)

February 7, 2010 03:10 PM Robert
I deleted the other attachment. Can you check the Console again for any new messages from build 37?

February 7, 2010 03:13 PM Tobias
There is still no output inside the Console.

February 7, 2010 03:18 PM Robert
Hm. This actually appears to be an issue with Xdebug 2.0.5 and PHP 5.3: http://bugs.xdebug.org/bug_view_page.php?bug_id=00000469 . You could try the 2.1 beta of Xdebug, but I haven't tested it at all.

February 7, 2010 03:23 PM Tobias
Upgrading to xdebug 2.1.0beta2 solved this issue. Thank you very much for your time!

February 7, 2010 03:36 PM Robert
I'm glad that worked. Please post new bugs with any incompatibilities you find with MacGDBp and Xdebug 2.1