Test failure tracing\\eventpipe\\bigevent\\bigevent\\bigevent.cmd

[v-wenyuxu]

Failed in: runtime-coreclr jitstress-isas-x86 20230422.1

Failed tests:

coreclr windows x64 Checked jitstress_isas_x86_nosse41 @ Windows.10.Amd64.Open
    - tracing\\eventpipe\\bigevent\\bigevent\\bigevent.cmd
coreclr windows x64 Checked jitstress_isas_x86_nohwintrinsic @ Windows.10.Amd64.Open
    - Loader\\binding\\tracing\\BinderTracingTest.ResolutionFlow\\BinderTracingTest.ResolutionFlow.cmd

�Error message:

 
Assert failure(PID 7984 [0x00001f30], Thread: 5188 [0x1444]): ep_rt_volatile_load_uint32_t (&buffer->state) == (uint32_t)EP_BUFFER_STATE_READ_ONLY

CORECLR! ep_buffer_manager_deallocate_buffers + 0x287 (0x00007ffc`f767dfc7)
CORECLR! ep_buffer_manager_free + 0x1B (0x00007ffc`f767e5db)
CORECLR! ep_session_free + 0xC8 (0x00007ffc`f7687e18)
CORECLR! disable_holding_lock + 0x65B (0x00007ffc`f767c7bb)
CORECLR! disable_helper + 0x134 (0x00007ffc`f767bf84)
CORECLR! ep_disable + 0x165 (0x00007ffc`f7681325)
CORECLR! ds_eventpipe_protocol_helper_handle_ipc_message + 0x263 (0x00007ffc`f768d653)
CORECLR! server_thread + 0x328 (0x00007ffc`f7692d58)
KERNEL32! BaseThreadInitThunk + 0x14 (0x00007ffd`28f684d4)
NTDLL! RtlUserThreadStart + 0x21 (0x00007ffd`29431791)
    File: D:\a\_work\1\s\src\native\eventpipe\ep-buffer.c Line: 60
    Image: C:\h\w\A36D0929\p\corerun.exe


Return code:      1
Raw output file:      C:\h\w\A36D0929\w\A0F208CB\uploads\Reports\tracing.eventpipe\bigevent\bigevent\bigevent.output.txt
Raw output:
BEGIN EXECUTION
 "C:\h\w\A36D0929\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  bigevent.dll 
  0.1s: ==TEST STARTING==
  1.6s: Started sending sentinel events...
  1.6s: Connecting to EventPipe...
  2.5s: Creating EventPipeEventSource...
  2.7s: EventPipeEventSource created
  2.8s: Dynamic.All callback registered
  2.8s: Running optional trace validator
  2.8s: Finished running optional trace validator
  2.8s: Starting stream processing...
  3.7s: Saw sentinel event
  3.7s: Starting event generating action...
  3.7s: Stopping event generating action
  3.7s: Sending StopTracing command...
  3.9s: Stopped sending sentinel events
  3.9s: Saw new provider 'BigEventSource'
  3.9s: Saw new provider 'Microsoft-DotNETCore-EventPipe'
  5.6s: Saw new provider 'Microsoft-Windows-DotNETRuntimeRundown'
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:\cores since 4/22/2023 10:14:57 PM
Processing C:\cores\corerun.exe.7984.dmp
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe -c "$<C:\h\w\A36D0929\t\tmp45eqvc.tmp" -z "C:\cores\corerun.exe.7984.dmp"
stdout: 
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\cores\corerun.exe.7984.dmp]
User Mini Dump File with Full Memory: Only application data is available


************* Path validation summary **************
Response                         Time (ms)     Location
OK                               16            C:\h\w\A36D0929\p\PDB
Symbol search path is: C:\h\w\A36D0929\p\PDB
Executable search path is: 
Windows 10 Version 14393 MP (4 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
10.0.14393.5125 (rs1_release.220429-1732)
Machine Name:
Debug session time: Sat Apr 22 22:15:09.000 2023 (UTC + 0:00)
System Uptime: 0 days 0:57:08.279
Process Uptime: 0 days 0:00:11.000
..............................................................

************* Symbol Loading Error Summary **************
Module name            Error
ntdll                  The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(1f30.1444): Unknown exception - code c0000602 (first/second chance not available)
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for coreclr.dll
KERNELBASE!RaiseFailFastException+0xae:
00007ffd`25e198ce 803d4d76120000  cmp     byt

�Stack trace:

    at tracing_eventpipe._bigevent_bigevent_bigevent_._bigevent_bigevent_bigevent_cmd()
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)

�

[tommcdon]

@davmason possible duplicate to #83575?