-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
behaviour diff: not all methods in RecursiveIteratorIterator class #404
Comments
We're closing out all bugs older than 2 months. http://www.hiphop-php.com/wp/?p=575 If this is still an issue, please re-open it, and in order of goodness:
|
huh, segfault with following code.
|
I didn't segfault on my box. Can you figure out what file is causing hhvm trouble? |
sudo mkdir /tmp/foo under gdb --args hhvm recursiveiteratoriterator.php , i got following: |
huh, bt:
|
Even with the directory you suggested I'm not seeing a segfault. Your backtrace looks like it is trying to get a property on a class. Can you compile a debug build, it should help diagnose much better. |
with commands do this? |
hhvm from current git, debug build:
may be you mail me with list of commands? |
Summary: fixes #404 Reviewed By: mjoras Differential Revision: D39189119 fbshipit-source-id: c31177c8e714e3ecd5ebfc85f5b1fcbca59e4060
Summary: X-link: facebook/mcrouter#404 Pull Request resolved: facebook#9337 Small build speed observation to avoid includes bloat. Differential Revision: D43330734 fbshipit-source-id: fed35bf8bab770072e384de9fe0a401f2b1260b4
Summary: X-link: facebook/mcrouter#404 Pull Request resolved: facebook#9337 Small build speed observation to avoid includes bloat. Differential Revision: D43330734 fbshipit-source-id: 3862749f86fb6c56102868c5745b6fbc89ab9763
Summary: X-link: facebook/mcrouter#404 Pull Request resolved: #9337 Small build speed observation to avoid includes bloat. Differential Revision: D43330734 fbshipit-source-id: 4393b37e5fee155eb58d61f00d3122b12772d73a
http://php.net/recursiveiteratoriterator
#403 note
The text was updated successfully, but these errors were encountered: