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

TIDs do not resolve for lttng ust events in traces with kernel traces. #77

Open
MatthewKhouzam opened this issue May 6, 2024 · 1 comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@MatthewKhouzam
Copy link
Contributor

MatthewKhouzam commented May 6, 2024

When a kernel and userspace trace are in an experiement, the userspace trace should have the TID resolved to the kernel's one as the information is present.

image

This is causing the new callstack to not resolve tids and not work as well as the incubator callstack. The missing analyes are in the incubator analysis core section:

@Override
protected void startActions() {
    TmfTraceUtils.registerEventAspect(AnalysisTidAspect.getInstance());
    TmfTraceUtils.registerEventAspect(AnalysisProcessNameAspect.getInstance());
    TmfTraceUtils.registerEventAspect(AnalysisThreadNameAspect.getInstance());
    TmfTraceUtils.registerEventAspect(AnalysisPidAspect.getInstance());
}

Here is a trace to test the results.

xz-52.zip

Blocks #76

@MatthewKhouzam MatthewKhouzam added good first issue Good for newcomers help wanted Extra attention is needed labels May 6, 2024
@MatthewKhouzam
Copy link
Contributor Author

It looks like replacing all trace.getEventAspects() with TmfTraceUtils.getEventAspects(trace,...) fixes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant