Windows error 0x00000085, 133

Detailed Error Information

IS_JOIN_TARGET[1]

MessageA JOIN or SUBST command cannot be used for a drive that contains previously joined drives.
Declared inwinerror.h

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

SETUP_FAILURE[2]

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

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 Code133 (0x0085)

Possible solutions

1

How to run fat binaries on iOS 5.1 / iPhone 4

objective-c
ios
jailbreak
armv7
armv6

PARTIALLY SOLVED :

Problem is that ldid can not sign fat binaries. See Building for Jailbroken devices on iOS SDK 4.2 for details.

I found this ldid source code that is supposed to sign fat binaries https://github.com/rpetrich/ldid but it does nor work for me (ldid hangs at runtime)

Solution probably is to use lipo tool to split the binary in two executables, ldid them separately and reassemble into one executable. (doesn't work for me either but I am working on it)

cd MyApp.app/; 
lipo MyApp -extract armv6 -output MyApp6; 
lipo MyApp -extract armv7 -output MyApp7; 
ldid -S MyApp6; ldid -S MyApp7; 
lipo -create MyApp6 MyApp7 -output MyApp
answered on Stack Overflow Mar 29, 2012 by S├ębastien Stormacq • edited May 23, 2017 by Community
0

DWARF - How to find the prologue end/epilogue start addresses of functions in a given binary?

c
assembly
objdump
dwarf
readelf

Try

readelf -wi

And look for DW_AT_low_pc and DW_AT_high_pc for the subroutine you are looking at.

The DWARF spec says:

A subroutine entry may have either a DW_AT_low_pc and DW_AT_high_pc pair of attributes or a DW_AT_ranges attribute whose values encode the contiguous or non-contiguous address ranges, respectively, of the machine instructions generated for the subroutine (see Section 2.17).

If I remember correctly, the DW_AT_low_pc is the address immediately after the prologue and DW_AT_high_pc is the last address before the epilogue.

Don't worry about the opcodes being 'special' that just means that they don't take arguments to save space in the encoded line number program.

answered on Stack Overflow Sep 28, 2014 by Torleif

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