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 ?
MacGDBp / 1.3.0
Status ?
Severity ?
Fixed in Revision ?
Mstone ?
Summary ?
v 1.3.0 Unusable
Report Time ?
May 19, 2009 04:53 PM
Assignment ?
Resolution ?
Priority ?
Dependencies ?
- none -
Mstone (old) ?

bug-167-crash_report-dhthomas.txt Crash report for bug 167
For: 0 (0%)
Against: 0 (0%)
Total: 0

May 19, 2009 04:53 PM djm
I upgraded from 1.2.1 and found 1.3.0 unusable due to hangs and crashes. Ive downgraded back to 1.2.1 for now. Mac OS 10.5.6 / PHP 5.2.9 / xdebug 2.0.4. I look forward to a new rev.

May 20, 2009 03:52 AM Robert
I noticed this too, today, when dog-fooding it :/. I've uploaded a test build here: http://www.bluestatic.org/bugs/showreport.php?bugid=166. Can you see if this resolves the issues for you?

May 28, 2009 11:41 AM olafure
I can confirm this. I just upgraded to 1.3.0 and it went unusable. Went back to 1.2.1 and happiness showed up again.
PHP seems to connect to macgdbp but both just hangs and when i press "Play" button in macgdbp it crashes.

Will be happy to help to resolve the issue if I can.

May 28, 2009 11:44 AM olafure
Robert: I just tested the build you mentioned, and it seems to be working!

May 28, 2009 11:44 AM Robert
Can you please test the build I posted in #166?

June 4, 2009 10:22 AM Jakob Stoeck
The build in #166 fixed the crashing for me.

June 5, 2009 07:37 PM djm
Robert: The build you posted in #166 is working for me. The inspector is a big help. Thx!

June 10, 2009 01:38 PM dhthomas
Sounds like you've got this one squashed, but just in case you need more info, here's a dump of the Apple report on my system.
About to try the test build you've created.
Thanks for your hard work.

June 10, 2009 01:44 PM dhthomas
Confirmed that the test build from bug 166 has resolved the issue for me.

July 22, 2009 03:26 AM Robert
I'm marking this as a duplicate of bug 166. Please watch that bug (favorite it for email notifications) because I'm going to post a new build in the next couple of days, which I hope will fix it (again). The build in #166 simply reverts the changes that were made to the socket layer, so it's not really a fix for the long-term.

On July 22, 2009 03:26 AM, Robert changed: