Windows error 0x000002EC, 748

Detailed Error Information

PAGE_FAULT_DEMAND_ZERO[1]

MessagePage fault was a demand zero fault.
Declared inwinerror.h

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

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 Code748 (0x02ec)

Possible solutions

1

Why is the string specified in `LD_PRELOAD` loaded on the memory of setuid executables in RedHat 6.2?

linux
security
memory
ld-preload

On Linux, all environment variables are visible to a program via a special third argument to main() traditionally called envp: http://crasseux.com/books/ctutorial/Environment-variables.html

If envp is part of your main() signature, it will point to an array containing all the environment variables. Even if it's not, it makes sense that the array might still exist in your program's address space.

None of this means that the loader actually respects LD_PRELOAD in any specific scenario--it is free to ignore it, e.g. under setuid, but the variable will still exist.

answered on Stack Overflow Jan 26, 2017 by John Zwinck
0

How to call std library functions in lldb

lldb

That's an instance method, you have to call it on an object. In your case, it looks like you want to do something like:

(lldb) expr ((std::__1::string *) $rax)->c_str()
(const value_type *) $1 = 0x00007fff5fbff661 "some string here"

You really shouldn't have to explicitly name the __1, but lldb doesn't support "inline namespaces" yet (and the clang debug information doesn't say __1 IS an inline namespace, so for now you do.

answered on Stack Overflow Nov 11, 2014 by Jim Ingham
0

Windows 7 Ultimate, death blue screen with new kingston memory

windows-7
memory
ddr2

With the first crash on th 9th clearly happening from a memory error, and the other two unhandled exceptions in drivers - and based on this happening with the addition of the memory, it seems strong that one (or both) of the two new memory sticks is bad. Your bios should have a boot time option to do extended memory diagnostics. Let that run over night. If it generates any error logs, request a replacement from the manufactor.

answered on Super User Feb 13, 2012 by jdh
0

Why is the string specified in `LD_PRELOAD` loaded on the memory of setuid executables in RedHat 6.2?

linux
security
memory
ld-preload

To elaborate a bit on John's answer, some env. variables are removed completely from setuid environment i.e. not passed to insecure subprocesses (e.g. LD_DEBUG) and some are plain ignored but passed to subprocesses (e.g. LD_PRELOAD).

answered on Stack Overflow Jan 26, 2017 by yugr

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