add optional offset argument to callStackGet()

Description

callStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace.

An optional offset argument (default 0, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace.

Also add optional argument maxFrames to limit the number of frames to return, with a default of 0 which means all frames.

https://docs.lucee.org/reference/functions/callstackget.html

Activity

Zac Spitzer
updated the Description
12 October 2021 at 14:57
callStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace. An optional {{offset}} argument (default 0, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace. Also add optional argument {{maxFrames}} to limit the number of frames to return, with a default of 0 which means all frames.
callStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace. An optional {{offset}} argument (default 0, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace. Also add optional argument {{maxFrames}} to limit the number of frames to return, with a default of 0 which means all frames. [https://docs.lucee.org/reference/functions/callstackget.html|https://docs.lucee.org/reference/functions/callstackget.html]
Zac Spitzer
updated the Workflow
4 February 2021 at 17:50
LDEV: Enhancement Workflow
LDEV: Enhancement Workflow V2
Igal Sapir
updated the Description
20 December 2020 at 21:39
callStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace. An optional {{offset}} argument (default 0, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace.
callStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace. An optional {{offset}} argument (default 0, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace. Also add optional argument {{maxFrames}} to limit the number of frames to return, with a default of 0 which means all frames.
Igal Sapir
changed the Status
20 December 2020 at 21:34
QA
Deployed
Igal Sapir
updated the Fix versions
20 December 2020 at 21:34
None
5.3.8.130
Igal Sapir
updated the Resolution
20 December 2020 at 21:34
None
Fixed
Igal Sapir
changed the Status
20 December 2020 at 21:33
In Development
QA
Igal Sapir
changed the Status
20 December 2020 at 21:33
Backlog
In Development
Igal Sapir
updated the Description
20 December 2020 at 19:56
CallStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace. An optional start argument (default 1, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace.
callStackGet() returns the stack trace, but many times if we use it from within an error handling function or framework, then those methods are added to the stack trace. An optional {{offset}} argument (default 0, meaning start at the beginning) will allow to skip the first #offset# calls from the stack trace.
Igal Sapir
updated the Summary
12 December 2020 at 01:30
add optional start argument to callStackGet()
add optional offset argument to callStackGet()
Igal Sapir
changed the Status
1 December 2020 at 02:51
New
Backlog
Igal Sapir
created the Work item
14 May 2017 at 19:25
Fixed

Details

Assignee

Reporter

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Fix versions

Priority

Created 14 May 2017 at 19:25
Updated 12 October 2021 at 14:57
Resolved 20 December 2020 at 21:34