Skip to content
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

Segfault under PHP 5.5 #115

Open
flack opened this issue Aug 26, 2013 · 10 comments
Open

Segfault under PHP 5.5 #115

flack opened this issue Aug 26, 2013 · 10 comments

Comments

@flack
Copy link
Member

flack commented Aug 26, 2013

I tried enabling php55 in openpsa travis tests today, unfortunately, it segfaults every time:

https://travis-ci.org/flack/openpsa/jobs/10626779#L1336

I don't have a local php55 installation available yet, so I can't post gdb output or anything like that, but I could try to set up a VM if it is necessary

@piotras
Copy link
Member

piotras commented Aug 26, 2013

Can you paste/attache php-midgard compile output? From travis of course. I do not see any in the link you provided.

@flack
Copy link
Member Author

flack commented Aug 26, 2013

It's there, but collapsed. I tried getting a direct link, but at least on my machine, it doesn't work. Maybe you have more luck:

https://travis-ci.org/flack/openpsa/jobs/10626779#L339

If not, just go to line 339 manually, the compile output should start there (you may need to expand the section with the little triangle thingie)

@piotras
Copy link
Member

piotras commented Aug 27, 2013

I tried to compile and run simple script on ubuntu. Works fine. No crashes. I think gdb/valgrind output is recommended.

@flack
Copy link
Member Author

flack commented Aug 27, 2013

I can try to set up a VM with php55 tonight or so, but if you have a working setup anyways, could you try running the openpsa test suite? It should be very simple, just clone the repo, run composer install (you can ignore the questions about DB setup by just pressing enter and ignoring the error messages), and then run phpunit. The segfault always seems to happen in the asgard copy test, so I would suspect that this triggers some code path in midgard that the others don't

@flack
Copy link
Member Author

flack commented Aug 27, 2013

I tried reproducing this locally now on a Kubuntu 13.04 VM. There, the segfault doesn't occur, so maybe it happens only on Ubuntu 12.04 (which is what Travis uses).

@piotras
Copy link
Member

piotras commented Aug 29, 2013

Travis uses own php builts. I think we can try valgrind directly there.
Install valgrind on travis. In tests/travis_midgard.sh add valgrind to apt-get install line.
Then wrap test script. Something like this:

valgrind -v --log-file=failure.log phpunit ; cat failure.log

@flack
Copy link
Member Author

flack commented Sep 1, 2013

It took a bit, but I now have valgrind ouput:

https://travis-ci.org/flack/openpsa/jobs/10859134#L1409

it starts on line 1409, in case the link doesn't take you to the right place

@piotras
Copy link
Member

piotras commented Sep 2, 2013

Valgrind output tells nothing :( I suspect PHP threads related issue. It's disabled by default everywhere and enabled on travis.

@flack
Copy link
Member Author

flack commented Sep 2, 2013

So, is there anything else we could try? For now, i can of course remove php55 from the build matrix, but sooner or later, it would be nice if we could run Travis tests against it

@piotras
Copy link
Member

piotras commented Sep 2, 2013

The only one option seems to be compile 5.5 with threads enabled and run tests with valgrind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants