-
Notifications
You must be signed in to change notification settings - Fork 393
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 options to control the costs of collecting thread stack traces #6629
Conversation
@babsingh : please review |
Allow separation of symbol resolution from collecting stack traces. Don't call introspect_backtrace_symbols() if OMR_INTROSPECT_NO_SYMBOLS is specified in J9ThreadWalkState.options given to omrintrospect_threads_*(). Add introspect_backtrace_symbols_ex() which accepts options, the first of which, OMR_BACKTRACE_SYMBOLS_BASIC, controls the cost of symbol resolution. Currently, this is only meaningful on Linux where full symbol resolution can be costly. Signed-off-by: Keith W. Campbell <keithc@ca.ibm.com>
Updated based on review feedback. |
jenkins build all |
The last successful plinux PR build was on July 19; all have failed since so I don't think it has anything to do with this. |
Yes, it is a known issue; unrelated to this PR. #6556 matches this failure. |
Pinged @AdamBrousseau since all OMR zOS nodes are offline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; will merge once the zOS build passes.
The zOS build has passed now. |
Allow separation of symbol resolution from collecting stack traces. Don't call
introspect_backtrace_symbols()
ifOMR_INTROSPECT_NO_SYMBOLS
is specified inJ9ThreadWalkState.options
given toomrintrospect_threads_*()
.Add
introspect_backtrace_symbols_ex()
which accepts options, the first of which,OMR_BACKTRACE_SYMBOLS_BASIC
, controls the cost of symbol resolution. Currently, this is only meaningful on Linux where full symbol resolution can be costly.