You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible when printing an error to only print the Callstack that is generated from this position onward, but ignore the Callstack that happened prior to the method that prints the error?
For instance if I am using a webserver, such as negroni, it includes a lot of function calls which happen before reaching my code. These calls are still included in the stack trace, and clutter it, but I am not particularly interested in them.
Is there a way to ignore them?
If there isn't at present, maybe something can be done to match the runtime.Callers at the printing location with the stack trace inside the error, and ignore the matching part?
On Sun, Mar 26, 2017 at 3:59 AM, e-nikolov ***@***.***> wrote:
Is it possible when printing an error to only print the Callstack that is
generated from this position onward, but ignore the Callstack that happened
prior to the method that prints the error?
For instance if I am using a webserver, such as negroni, it includes a lot
of function calls which happen before reaching my code. These calls are
still included in the stack trace, and clutter it, but I am not
particularly interested in them.
Is there a way to ignore them?
If there isn't at present, maybe something can be done to match the
runtime.Callers at the printing location with the stack trace inside the
error, and ignore the matching part?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#111>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAcAzxL-p49NBbeeD4L1jhGh-9aAV7Bks5rpUgLgaJpZM4MpI3s>
.
Activity
davecheney commentedon Mar 29, 2017