Windows error 0x00000113, 275

Detailed Error Information

EAS_DIDNT_FIT[1]

MessageThe extended attributes did not fit in the buffer.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070113.

VIDEO_DXGKRNL_FATAL_ERROR[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x113: VIDEO_DXGKRNL_FATAL_ERROR.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code275 (0x0113)

Possible solutions

6

ABI Register Names for RISC-V Calling Convention

riscv

The stack pointer is now x2.

Here is the current ABI documentation, which has been moved out of the User-Level ISA specification, which now contains that same link.

The ABI was modified to better accommodate the new RISC-V compressed spec, which puts the 8 most-used registers next to each other in x8-x15.

Note: do not trust ANY non riscv.org webpage. Quan Nguyen makes this clear in his introduction that the "RISC-V Linux User's Manual" is for documenting the porting process and that accuracy is NOT guaranteed.

answered on Stack Overflow Jun 4, 2015 by Chris • edited Dec 7, 2017 by Aaron Muir Hamilton
1

iOS 4.3 distribution binary no longer working with iPhone 3G/2nd Gen iPod Touch?

iphone
ios
ios4
crash
ipod-touch

iOS 4.3 is not supported on devices older than iPhone 3GS and iPod Touch 3rd Gen (excluding the 8GB model, which is also not supported).

Source: Apple.com (scroll to bottom)

answered on Stack Overflow Apr 20, 2011 by Christian
0

RISC-V disassembler doesn't match with spike running results?

gcc
assembly
compilation
riscv
disassembly

I think that in spike you see start of boot process and the pk binary (in physical addresses). And in objdump output you have ELF disassembled from the entry point. So hello binary may be somewhere later in spike output...

What you see from spike resemble me this code of machine init: https://github.com/riscv/riscv-pk/blob/6c1d0604dcabf36a6a8d8d9a839b2d4634e202d2/machine/mentry.S#L183

core   0: 0x0000000000001000 (0x7ffff297) auipc   t0, 0x7ffff
:  
core   0: 0x0000000000001004 (0x00028067) jr      t0

reset_vector:
  j do_reset

and then exact do_reset of machine/mentry.S (line 183), it is still before main pk code, before loading and running user app hello:

do_reset:
  li x1, 0
  li x2, 0
  li x3, 0
  li x4, 0
  li x5, 0
  li x6, 0
  li x7, 0
  li x8, 0
  li x9, 0
  li x10, 0
  li x11, 0
  li x12, 0
  li x13, 0
  li x14, 0
  li x15, 0
  li x16, 0
  li x17, 0
  li x18, 0
  li x19, 0
  li x20, 0
  li x21, 0
  li x22, 0
  li x23, 0
  li x24, 0
  li x25, 0
  li x26, 0
  li x27, 0
  li x28, 0
  li x29, 0
  li x30, 0
  li x31, 0
  csrw mscratch, x0

  # write mtvec and make sure it sticks
  la t0, trap_vector
  csrw mtvec, t0
  csrr t1, mtvec
1:bne t0, t1, 1b
answered on Stack Overflow Mar 15, 2017 by osgx

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0