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

Add support for 'startFrame' parameter in stack trace. #312

Merged

Conversation

brownts
Copy link
Collaborator

@brownts brownts commented Feb 28, 2022

Fixes #308.

When a stack trace contains many functions calls, the 'startFrame' can
be used in subsequent calls to expand a subset of the complete stack
trace. Although this parameter is optional, if not utilized, it can
prohibit the interrogation of a long list of stack frames when
combined with the 'levels' parameter.

@GitMensch
Copy link
Collaborator

I may get a bit lazy, but do you mind adding the Changelog here, too? I'd merge that tomorrow.

@brownts
Copy link
Collaborator Author

brownts commented Mar 3, 2022

No problem, I'll add that and rebase on the latest.

When a stack trace contains many functions calls, the 'startFrame' can
be used in subsequent calls to expand a subset of the complete stack
trace.  Although this parameter is optional, if not utilized, it can
prohibit the interrogation of a long list of stack frames when
combined with the 'levels' parameter.
@brownts brownts force-pushed the bugfix/stack_trace_start_frame branch from 0eaff28 to d8c6c02 Compare March 3, 2022 14:18
@GitMensch GitMensch merged commit 2200ae7 into WebFreak001:master Mar 4, 2022
@GitMensch
Copy link
Collaborator

Thanks for another nice contribution!

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

Successfully merging this pull request may close these issues.

Long call stacks don't display properly, loop initial elements infinitely
2 participants