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 options to control the costs of collecting thread stack traces #6629

Merged
merged 1 commit into from
Aug 3, 2022

Conversation

keithc-ca
Copy link
Member

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.

@0xdaryl
Copy link
Contributor

0xdaryl commented Jul 28, 2022

@babsingh : please review

@babsingh babsingh requested review from babsingh and removed request for rwy7, youngar, mstoodle and charliegracie July 28, 2022 20:08
port/common/omrosbacktrace.c Outdated Show resolved Hide resolved
include_core/omrport.h Outdated Show resolved Hide resolved
include_core/omrport.h Outdated Show resolved Hide resolved
port/ztpf/omrosbacktrace_impl.c Outdated Show resolved Hide resolved
port/common/omrosbacktrace.c Outdated Show resolved Hide resolved
port/common/omrosbacktrace.c Outdated Show resolved Hide resolved
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>
@keithc-ca
Copy link
Member Author

Updated based on review feedback.

@babsingh
Copy link
Contributor

babsingh commented Aug 3, 2022

jenkins build all

@keithc-ca
Copy link
Member Author

keithc-ca commented Aug 3, 2022

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.
Perhaps #6556?

@babsingh
Copy link
Contributor

babsingh commented Aug 3, 2022

https://ci.eclipse.org/omr/job/PullRequest-linux_ppc-64_le_gcc/3727/console

Yes, it is a known issue; unrelated to this PR. #6556 matches this failure.

@babsingh
Copy link
Contributor

babsingh commented Aug 3, 2022

Pinged @AdamBrousseau since all OMR zOS nodes are offline.

Copy link
Contributor

@babsingh babsingh left a 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.

@pshipton
Copy link
Member

pshipton commented Aug 3, 2022

The zOS build has passed now.

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.

None yet

4 participants