package tracev2

Import Path
	internal/trace/tracev2 (on go.dev)

Dependency Relation
	imports 0 packages, and imported by 6 packages

Involved Source Files

	  d doc.go
		Package tracev2 contains definitions for the v2 execution trace wire format.
		
		These definitions are shared between the trace parser and the runtime, so it
		must not depend on any package that depends on the runtime (most packages).

	    events.go
	    spec.go
Package-Level Type Names (total 5)

	/* sort by: alphabet | popularity */
	 type EventSpec (struct)
		EventSpec is a specification for a trace event. It contains sufficient information
		to perform basic parsing of any trace event for any version of Go.

		Fields (total 9)
			Args []string
				Args contains the names of each trace event's argument.
				Its length determines the number of arguments an event has.
				
				Argument names follow a certain structure and this structure
				is relied on by the testing framework to type-check arguments
				and to produce Values for experimental events.
				
				The structure is:
				
				    (?P<name>[A-Za-z]+)(_(?P<type>[A-Za-z]+))?
				
				In sum, it's a name followed by an optional type.
				If the type is present, it is preceded with an underscore.
				Arguments without types will be interpreted as just raw uint64s.
				The valid argument types and the Go types they map to are listed
				in the ArgTypes variable.

			Experiment Experiment
				Experiment indicates the ID of an experiment this event is associated
				with. If Experiment is not NoExperiment, then the event is experimental
				and will be exposed as an EventExperiment.

			HasData bool
				HasData is true if the event has trailer consisting of a
				varint length followed by unencoded bytes of some data.
				
				An event may not be both a timed event and have data.

			IsStack bool
				IsStack indicates that the event represents a complete
				stack trace. Specifically, it means that after the arguments
				there's a varint length, followed by 4*length varints. Each
				group of 4 represents the PC, file ID, func ID, and line number
				in that order.

			IsTimedEvent bool
				IsTimedEvent indicates whether this is an event that both
				appears in the main event stream and is surfaced to the
				trace reader.
				
				Events that are not "timed" are considered "structural"
				since they either need significant reinterpretation or
				otherwise aren't actually surfaced by the trace reader.

			Name string
				Name is the human-readable name of the trace event.

			StackIDs []int
				StackIDs indicates which of the arguments are stack IDs.
				
				The list is not sorted. The first index always refers to
				the main stack for the current execution context of the event.

			StartEv EventType
				StartEv indicates the event type of the corresponding "start"
				event, if this event is an "end," for a pair of events that
				represent a time range.

			StringIDs []int
				StringIDs indicates which of the arguments are string IDs.

		As Outputs Of (at least 2)
			func Specs() []EventSpec
			func internal/trace/version.Version.Specs() []EventSpec
		As Inputs Of (at least one exported)
			func EventNames(specs []EventSpec) map[string]EventType

	 type EventType uint8 (basic type)
		EventType indicates an event's type from which its arguments and semantics can be
		derived. Its representation matches the wire format's representation of the event
		types that precede all event data.

		Methods (only one)
			( EventType) Experimental() bool
		As Outputs Of (at least one exported)
			func EventNames(specs []EventSpec) map[string]EventType
		As Inputs Of (at least 3)
			func internal/trace/internal/testgen.(*Batch).RawEvent(typ EventType, data []byte, args ...uint64)
			func internal/trace/internal/testgen.(*Trace).RawEvent(typ EventType, data []byte, args ...uint64)
			func internal/trace/version.Version.EventName(typ EventType) string
		As Types Of (total 66)
			const EvClockSnapshot
			const EvCPUSample
			const EvCPUSamples
			const EvEndOfGeneration
			const EvEventBatch
			const EvExperimentalBatch
			const EvFrequency
			const EvGCActive
			const EvGCBegin
			const EvGCEnd
			const EvGCMarkAssistActive
			const EvGCMarkAssistBegin
			const EvGCMarkAssistEnd
			const EvGCSweepActive
			const EvGCSweepBegin
			const EvGCSweepEnd
			const EvGoBlock
			const EvGoCreate
			const EvGoCreateBlocked
			const EvGoCreateSyscall
			const EvGoDestroy
			const EvGoDestroySyscall
			const EvGoLabel
			const EvGoroutineStack
			const EvGoroutineStackAlloc
			const EvGoroutineStackFree
			const EvGoStart
			const EvGoStatus
			const EvGoStatusStack
			const EvGoStop
			const EvGoSwitch
			const EvGoSwitchDestroy
			const EvGoSyscallBegin
			const EvGoSyscallEnd
			const EvGoSyscallEndBlocked
			const EvGoUnblock
			const EvHeapAlloc
			const EvHeapGoal
			const EvHeapObject
			const EvHeapObjectAlloc
			const EvHeapObjectFree
			const EvNone
			const EvProcsChange
			const EvProcStart
			const EvProcStatus
			const EvProcSteal
			const EvProcStop
			const EvSpan
			const EvSpanAlloc
			const EvSpanFree
			const EvStack
			const EvStacks
			const EvString
			const EvStrings
			const EvSTWBegin
			const EvSTWEnd
			const EvSync
			const EvUserLog
			const EvUserRegionBegin
			const EvUserRegionEnd
			const EvUserTaskBegin
			const EvUserTaskEnd
			const MaxEvent
			const MaxExperimentalEvent
			const NumEvents
			const NumExperimentalEvents

	 type Experiment uint (basic type)
		Experiment is an experiment ID that events may be associated with.

		As Types Of (total 3)
			const AllocFree
			const NoExperiment
			const NumExperiments

	 type GoStatus uint8 (basic type)
		GoStatus is the status of a goroutine.
		
		They correspond directly to the various goroutine states.

		Methods (only one)
			( GoStatus) String() string
		Implements (at least 2)
			 GoStatus : expvar.Var
			 GoStatus : fmt.Stringer
		As Types Of (total 5)
			const GoBad
			const GoRunnable
			const GoRunning
			const GoSyscall
			const GoWaiting

	 type ProcStatus uint8 (basic type)
		ProcStatus is the status of a P.
		
		They mostly correspond to the various P states.

		Methods (only one)
			( ProcStatus) String() string
		Implements (at least 2)
			 ProcStatus : expvar.Var
			 ProcStatus : fmt.Stringer
		As Types Of (total 5)
			const ProcBad
			const ProcIdle
			const ProcRunning
			const ProcSyscall
			const ProcSyscallAbandoned


Package-Level Functions (total 3)

	 func EventNames(specs []EventSpec) map[string]EventType
		EventNames is a helper that produces a mapping of event names to event types.

	 func Experiments() []string
	 func Specs() []EventSpec
Package-Level Variables (only one)

	  var EventArgTypes [10]string
		EventArgTypes is a list of valid argument types for use in Args.
		
		See the documentation of Args for more details.


Package-Level Constants (total 83)

	const AllocFree Experiment = 1
		AllocFree is the alloc-free events experiment.

	const EvClockSnapshot EventType = 51 // snapshot of trace, mono and wall clocks [timestamp, mono, sec, nsec]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvCPUSample EventType = 7 // CPU profiling sample [timestamp, M ID, P ID, goroutine ID, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvCPUSamples EventType = 6 // start of a section of CPU samples [...EvCPUSample]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvEndOfGeneration EventType = 52
		Reserved internal in-band end-of-generation signal. Must never appear in the trace. Added in Go 1.25.
		This could be used as an explicit in-band end-of-generation signal in the future.

	const EvEventBatch EventType = 1 // start of per-M batch of events [generation, M ID, timestamp, batch length]
		Structural events.

	const EvExperimentalBatch EventType = 49 // start of extra data [experiment ID, generation, M ID, timestamp, batch length, batch data...]
		Batch event for an experimental batch with a custom format. Added in Go 1.23.

	const EvFrequency EventType = 8 // timestamp units per sec [freq]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCActive EventType = 28 // GC active [timestamp, seq]
		GC events.

	const EvGCBegin EventType = 29 // GC start [timestamp, seq, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCEnd EventType = 30 // GC done [timestamp, seq]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCMarkAssistActive EventType = 34 // GC mark assist active [timestamp, goroutine ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCMarkAssistBegin EventType = 35 // GC mark assist start [timestamp, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCMarkAssistEnd EventType = 36 // GC mark assist done [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCSweepActive EventType = 31 // GC sweep active [timestamp, P ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCSweepBegin EventType = 32 // GC sweep start [timestamp, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGCSweepEnd EventType = 33 // GC sweep done [timestamp, swept bytes, reclaimed bytes]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoBlock EventType = 20 // goroutine blocks [timestamp, reason, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoCreate EventType = 14 // goroutine creation [timestamp, new goroutine ID, new stack ID, stack ID]
		Goroutines.

	const EvGoCreateBlocked EventType = 47 // goroutine creation (starts blocked) [timestamp, new goroutine ID, new stack ID, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoCreateSyscall EventType = 15 // goroutine appears in syscall (cgo callback) [timestamp, new goroutine ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoDestroy EventType = 17 // goroutine ends [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoDestroySyscall EventType = 18 // goroutine ends in syscall (cgo callback) [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoLabel EventType = 39 // apply string label to current running goroutine [timestamp, label string ID]
		Annotations.

	const EvGoroutineStack EventType = 134 // stack exists [timestamp, id, order]
		Experimental goroutine stack events. Added in Go 1.23.

	const EvGoroutineStackAlloc EventType = 135 // stack alloc [timestamp, id, order]
		Experimental events.

	const EvGoroutineStackFree EventType = 136 // stack free [timestamp, id]
		Experimental events.

	const EvGoStart EventType = 16 // goroutine starts running [timestamp, goroutine ID, goroutine seq]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoStatus EventType = 25 // goroutine status at the start of a generation [timestamp, goroutine ID, thread ID, status]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoStatusStack EventType = 48 // goroutine status at the start of a generation, with a stack [timestamp, goroutine ID, M ID, status, stack ID]
		GoStatus with stack. Added in Go 1.23.

	const EvGoStop EventType = 19 // goroutine yields its time, but is runnable [timestamp, reason, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoSwitch EventType = 45 // goroutine switch (coroswitch) [timestamp, goroutine ID, goroutine seq]
		Coroutines. Added in Go 1.23.

	const EvGoSwitchDestroy EventType = 46 // goroutine switch and destroy [timestamp, goroutine ID, goroutine seq]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoSyscallBegin EventType = 22 // syscall enter [timestamp, P seq, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoSyscallEnd EventType = 23 // syscall exit [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoSyscallEndBlocked EventType = 24 // syscall exit and it blocked at some point [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvGoUnblock EventType = 21 // goroutine is unblocked [timestamp, goroutine ID, goroutine seq, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvHeapAlloc EventType = 37 // gcController.heapLive change [timestamp, heap alloc in bytes]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvHeapGoal EventType = 38 // gcController.heapGoal() change [timestamp, heap goal in bytes]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvHeapObject EventType = 131 // heap object exists [timestamp, id, type]
		Experimental heap object events. Added in Go 1.23.

	const EvHeapObjectAlloc EventType = 132 // heap object alloc [timestamp, id, type]
		Experimental events.

	const EvHeapObjectFree EventType = 133 // heap object free [timestamp, id]
		Experimental events.

	const EvNone EventType = 0 // unused
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvProcsChange EventType = 9 // current value of GOMAXPROCS [timestamp, GOMAXPROCS, stack ID]
		Procs.

	const EvProcStart EventType = 10 // start of P [timestamp, P ID, P seq]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvProcStatus EventType = 13 // P status at the start of a generation [timestamp, P ID, status]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvProcSteal EventType = 12 // P was stolen [timestamp, P ID, P seq, M ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvProcStop EventType = 11 // stop of P [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvSpan EventType = 128 // heap span exists [timestamp, id, npages, type/class]
		Experimental heap span events. Added in Go 1.23.

	const EvSpanAlloc EventType = 129 // heap span alloc [timestamp, id, npages, type/class]
		Experimental events.

	const EvSpanFree EventType = 130 // heap span free [timestamp, id]
		Experimental events.

	const EvStack EventType = 3 // stack table entry [ID, ...{PC, func string ID, file string ID, line #}]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvStacks EventType = 2 // start of a section of the stack table [...EvStack]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvString EventType = 5 // string dictionary entry [ID, length, string]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvStrings EventType = 4 // start of a section of the string dictionary [...EvString]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvSTWBegin EventType = 26 // STW start [timestamp, kind]
		STW.

	const EvSTWEnd EventType = 27 // STW done [timestamp]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvSync EventType = 50 // start of a sync batch [...EvFrequency|EvClockSnapshot]
		Sync batch. Added in Go 1.25. Previously a lone EvFrequency event.

	const EvUserLog EventType = 44 // trace.Log [timestamp, internal task ID, key string ID, value string ID, stack]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvUserRegionBegin EventType = 42 // trace.{Start,With}Region [timestamp, internal task ID, name string ID, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvUserRegionEnd EventType = 43 // trace.{End,With}Region [timestamp, internal task ID, name string ID, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvUserTaskBegin EventType = 40 // trace.NewTask [timestamp, internal task ID, internal parent task ID, name string ID, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const EvUserTaskEnd EventType = 41 // end of a task [timestamp, internal task ID, stack ID]
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const GoBad GoStatus = 0
	const GoRunnable GoStatus = 1
	const GoRunning GoStatus = 2
	const GoSyscall GoStatus = 3
	const GoWaiting GoStatus = 4
	const MaxBatchSize = 65536
		MaxBatchSize sets the maximum size that a batch can be.
		
		Directly controls the trace batch size in the runtime.
		
		NOTE: If this number decreases, the trace format version must change.

	const MaxEvent EventType = 127
		Experimental events.

	const MaxEventTrailerDataSize = 1024
		MaxEventTrailerDataSize controls the amount of trailer data that
		an event can have in bytes. Must be smaller than MaxBatchSize.
		Controls the maximum string size in the trace.
		
		Directly controls the maximum such value in the runtime.
		
		NOTE: If this number decreases, the trace format version must change.

	const MaxExperimentalEvent EventType = 137
		Experimental events.

	const MaxFramesPerStack = 128
		Maximum number of PCs in a single stack trace.
		
		Since events contain only stack ID rather than whole stack trace,
		we can allow quite large values here.
		
		Directly controls the maximum number of frames per stack
		in the runtime.
		
		NOTE: If this number decreases, the trace format version must change.

	const MaxTimedEventArgs = 5
		MaxTimedEventArgs is the maximum number of arguments for timed events.

	const NoExperiment Experiment = 0
		NoExperiment is the reserved ID 0 indicating no experiment.

	const NumEvents EventType = 53
		Event types in the trace, args are given in square brackets.
		
		Naming scheme:
		  - Time range event pairs have suffixes "Begin" and "End".
		  - "Start", "Stop", "Create", "Destroy", "Block", "Unblock"
		    are suffixes reserved for scheduling resources.
		
		NOTE: If you add an event type, make sure you also update all
		tables in this file!

	const NumExperimentalEvents EventType = 10
	const NumExperiments Experiment = 2
		Experiments.

	const ProcBad ProcStatus = 0
	const ProcIdle ProcStatus = 2
	const ProcRunning ProcStatus = 1
	const ProcSyscall ProcStatus = 3
	const ProcSyscallAbandoned ProcStatus = 4
		ProcSyscallAbandoned is a special case of
		ProcSyscall. It's used in the very specific case
		where the first a P is mentioned in a generation is
		part of a ProcSteal event. If that's the first time
		it's mentioned, then there's no GoSyscallBegin to
		connect the P stealing back to at that point. This
		special state indicates this to the parser, so it
		doesn't try to find a GoSyscallEndBlocked that
		corresponds with the ProcSteal.

The pages are generated with Golds v0.7.7-preview. (GOOS=linux GOARCH=amd64)
Golds is a Go 101 project developed by Tapir Liu.
PR and bug reports are welcome and can be submitted to the issue list.
Please follow @zigo_101 (reachable from the left QR code) to get the latest news of Golds.