Cannot run runtime tests with lttng 2.13

[ManickaP]

AFAIU the problem, the officially released runtime is linked with lttng 2.12, while current version is 2.13 LTTng 2.13 "Nordicité" (current release).

As a result, when I try to run tests in runtime libraries, e.g.: dotnet build /t:test in System.Net.Http functional tests, the process crashes with:

 exit code 139 means SIGSEGV Illegal memory access. Deref invalid pointer, overrunning buffer, stack overflow etc. Core dumped.

Dump:

* thread #1, name = 'dotnet', stop reason = signal SIGSEGV
  * frame #0: 0x00007ff73baa4682 liblttng-ust.so.1`lttng_ust_probe_register + 162
    frame #1: 0x00007ff73bb631f5 libcoreclrtraceptprovider.so`lttng_ust__events_init__DotNETRuntime() at ust-tracepoint-event.h:1198:14
...

I'm just a first person hitting this since I'm on Arch, but it's highly likely this will affect others in the future as well.

I'd be glad even for a hacky workaround since this is blocking for me.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

AFAIU the problem, the officially released runtime is linked with lttng 2.12, while current version is 2.13 LTTng 2.13 "Nordicité" (current release).

As a result, when I try to run tests in runtime libraries, e.g.: dotnet build /t:test in System.Net.Http functional tests, the process crashes with:

 exit code 139 means SIGSEGV Illegal memory access. Deref invalid pointer, overrunning buffer, stack overflow etc. Core dumped.

Dump:

* thread #1, name = 'dotnet', stop reason = signal SIGSEGV
  * frame #0: 0x00007ff73baa4682 liblttng-ust.so.1`lttng_ust_probe_register + 162
    frame #1: 0x00007ff73bb631f5 libcoreclrtraceptprovider.so`lttng_ust__events_init__DotNETRuntime() at ust-tracepoint-event.h:1198:14
...

I'm just a first person hitting this since I'm on Arch, but it's highly likely this will affect others in the future as well.

I'd be glad even for a hacky workaround since this is blocking for me.

Author:	ManickaP
Assignees:	-
Labels:	area-Infrastructure, untriaged
Milestone:	-

[am11]

Possible duplicate of #57784.

[thhous-msft]

You should be able to disable lttng by creating a DOTNET_LTTng=0 or COMPlus_LTTng=0 env var, which will disable loading the logging provider.

[ManickaP]

@am11 Thanks, this is a 100% dupe of that issue. Seeing the date of creation (19.8.) it corresponds with me reporting it internally. I just wasn't aware of the issue.

@thhous-msft Thanks for the workaround, it worked!

[ManickaP]

Duplicate of #57784