Windows error 0x000002FE, 766

Detailed Error Information

DBG_EXCEPTION_HANDLED[1]

MessageDebugger handled exception
Declared inwinerror.h

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

HRESULT analysis[2]

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[2][1]
DescriptionThe default facility code.[2][1]
Error Code766 (0x02fe)

Questions

2votes
1answer

Obtaining accurate heap usage in Windows (for debugging memory leaks in a single process)

I've worked for years as an embedded SW developer, in which memory leaks (even minimal amounts of memory) were often really critical. In these environments usually it was possible to evaluate the amount of used heap, and this made possible at least a rudimentary/rough memory-leak debugging just by printing the [...] read more
c++
windows
memory
memory-leaks
0votes
0answers

bomb lab phase_6 stuck

<+0>: push %r13 <+2>: push %r12 <+4>: push %rbp <+5>: push %rbx <+6>: sub $0x68,%rsp <+10>: mov %fs:0x28,%rax <+19>: mov %rax,0x58(%rsp) <+24>: xor %eax,%eax <+26>: mov %rsp,%r12 <+29>: mov %r12,%rsi <+32>: callq 0x5555555558cc <read_six_numbers> <+37>: mov $0x0,%r13d <+43>: jmp 0x555555555594 <phase_6+82> <+45>: callq 0x5555555558a6 <explode_bomb> <+50>: jmp 0x5555555555a3 <phase_6+97> <+52>: [...] read more
assembly
x86
reverse-engineering

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0