Windows error 0x00000277, 631

Detailed Error Information

FLOAT_MULTIPLE_TRAPS[1]

MessageMultiple floating point traps.
Declared inwinerror.h

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

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 Code631 (0x0277)

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

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
-1

difficulty listing threads/stacks with GDB on ARM

debugging
gcc
gdb
arm
remote-desktop

Do you have a reason to expect those threads to be executing your code? Quite often, threads are running library code or sleeping, and in either case they're not running your code. However, when you set a breakpoint in you code, it's only hit when that thread actually runs your code.

I'd bet you would see some of your code on some stack traces, though. Check it out; it will be enlightening.

answered on Stack Overflow Sep 6, 2011 by MSalters

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