Skip to content

Fix debug backtrace frameno #8761

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

Merged
merged 1 commit into from
Sep 29, 2022
Merged

Conversation

twose
Copy link
Member

@twose twose commented Jun 13, 2022

The frame may be skipped in some cases, and the trace may be truncated before exceeding the limit.

The frame may be skipped in some cases, and the trace may be truncated before exceeding the limit.
@mvorisek
Copy link
Contributor

no test?

@twose
Copy link
Member Author

twose commented Jun 14, 2022

no test?

Sorry, this is a problem I met a long time ago in the extension, it doesn't fire through existing PHP code, I need to test it in zend_test, I just opened the PR to see if it would affect existing tests first.
I will add a test for it later today.

@twose
Copy link
Member Author

twose commented Jun 14, 2022

Well, I took a little time to try it out and I found that I couldn't construct such a test quickly, and I would be very grateful if someone could help me to do that, or allow me to try it later.

@devnexen devnexen requested a review from iluuu1994 July 12, 2022 17:25
@iluuu1994
Copy link
Member

iluuu1994 commented Sep 29, 2022

Looking at 450f2ff it seems this only happens with phar files. Creating a test is probably not worth it, the fix looks and correct.

@iluuu1994 iluuu1994 merged commit fc37a82 into php:master Sep 29, 2022
@twose twose deleted the fix_debug_backtrace branch November 7, 2022 05:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants