Struct minidump_writer::minidump_format::format::XSTATE_CONFIG_FEATURE_MSC_INFO

pub struct XSTATE_CONFIG_FEATURE_MSC_INFO {
    pub size_of_info: u32,
    pub context_size: u32,
    pub enabled_features: u64,
    pub features: [XSTATE_FEATURE; 64],
}

A descriptor of the XSAVE context, which extends a normal x86/x64 context.

The sections of this context are dumps of some of the CPUs registers (e.g. one section might contain the contents of the SSE registers).

Intel documents its XSAVE entries in Volume 1, Chapter 13 of the “Intel 64 and IA-32 Architectures Software Developer’s Manual”.

The XSTATE Format in Minidumps

This format is slightly messed up in the context of minidumps because it’s grafted onto Microsoft’s own formats. Here’s what’s important to know:

• The “Cpu Context” and the “XSAVE context” are in fact the same regions of memory.

• Whether XSTATE is present or not, the classic layouts of CONTEXT_X86 and CONTEXT_AMD64 both apply – xstate will only add stuff after or refine your understanding of memory in the existing layout. So you can safely ignore the existence of XSTATE, but you might be missing new info.

• AMD64 doesn’t have a standard way to save general purpose registers, so the first 256 bytes of CONTEXT_AMD64 are just however microsoft decided to save the registers, and will not be referred to by the XSTATE.

!!! THIS PART IS IMPORTANT !!!

• As a consequence, all XSTATE_FEATURE::offset values must have 256 added to them to get the correct offset for that feature! For example, the LEGACY_FLOATING_POINT feature should always have an offset of 0, but it is actually at offset 256 in CONTEXT_AMD64 (it corresponds to CONTEXT_AMD64::float_save).

• The following features are already contained inside of CONTEXT_AMD64:

  • LEGACY_FLOATING_POINT
  • LEGACY_SSE
  • GSSE_AND_AVX

• If there are XSTATE entries that actually map outside of the context’s normal memory range, then the context’s context_flags will have bit 0x40 set (CONTEXT_HAS_XSTATE).

• ContextFlagsCpu::from_flags will mask out the CONTEXT_HAS_XSTATE bit. If you want to check for that bit, check the raw value of context_flags.

Fields

size_of_info: u32

The size of this struct.

context_size: u32

The size of the XSAVE context.

enabled_features: u64

The bit enabled_features[i] indicates that features[i] contains valid data.

features: [XSTATE_FEATURE; 64]

The offset and size of each XSAVE entry inside the XSAVE context.

Implementations

impl XSTATE_CONFIG_FEATURE_MSC_INFO

pub fn iter(&self) -> XstateFeatureIter<'_>

Gets an iterator of all the enabled features.

Trait Implementations

impl Clone for XSTATE_CONFIG_FEATURE_MSC_INFO

fn clone(&self) -> XSTATE_CONFIG_FEATURE_MSC_INFO

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for XSTATE_CONFIG_FEATURE_MSC_INFO

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Default for XSTATE_CONFIG_FEATURE_MSC_INFO

fn default() -> XSTATE_CONFIG_FEATURE_MSC_INFO

Returns the “default value” for a type.

impl SizeWith<Endian> for XSTATE_CONFIG_FEATURE_MSC_INFO

fn size_with(ctx: &Endian) -> usize

impl<'a> TryFromCtx<'a, Endian> for XSTATE_CONFIG_FEATURE_MSC_INFO

where XSTATE_CONFIG_FEATURE_MSC_INFO: 'a,

type Error = Error

fn try_from_ctx( src: &'a [u8], ctx: Endian ) -> Result<(XSTATE_CONFIG_FEATURE_MSC_INFO, usize), <XSTATE_CONFIG_FEATURE_MSC_INFO as TryFromCtx<'a, Endian>>::Error>

impl<'a> TryIntoCtx<Endian> for &'a XSTATE_CONFIG_FEATURE_MSC_INFO

type Error = Error

fn try_into_ctx( self, dst: &mut [u8], ctx: Endian ) -> Result<usize, <&'a XSTATE_CONFIG_FEATURE_MSC_INFO as TryIntoCtx<Endian>>::Error>

impl TryIntoCtx<Endian> for XSTATE_CONFIG_FEATURE_MSC_INFO

type Error = Error

fn try_into_ctx( self, dst: &mut [u8], ctx: Endian ) -> Result<usize, <XSTATE_CONFIG_FEATURE_MSC_INFO as TryIntoCtx<Endian>>::Error>