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.

Sign up for GitHub

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

Jump to bottom

Do I always have to call timecop::return? #53

Open

glassmonkey opened this issue Jun 21, 2021 · 0 comments

glassmonkey commented Jun 21, 2021 •

edited

Loading

If I use timecop::freeze in a test, do I always have to call timecop::return? (e.g. call in tearDown).

If I run the test without timecop::return, I get a segmentation fault.

#0 0x00005645648f3384 in zend_call_method ()
#1 0x00007fb914ea0c8a in _timecop_datetime_constructor_ex.isra.7 () from /usr/lib64/php/modules/timecop.so
#2 0x00007fb924300dd5 in xdebug_execute_internal () from /usr/lib64/php/modules/xdebug.so
#3 0x00005645646ce7b4 in ZEND_DO_FCALL_SPEC_RETVAL_UNUSED_HANDLER ()
#4 0x000056456495f5a6 in execute_ex ()

(omitted below)
```

The text was updated successfully, but these errors were encountered:

glassmonkey changed the title ~~Always call timecop::return?~~ do I always have to call timecop::return?

glassmonkey changed the title ~~do I always have to call timecop::return?~~ Do I always have to call timecop::return?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment