This is probably not the correct interpretation of this error.
The Win32 error above is more likely to indicate the actual problem.
Flags
Severity
Success
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.
enter image description here [https://i.stack.imgur.com/ZKl0f.jpg] I have a water cooled system, but.... I don't have that kind of wallet to be able to pull that out. Is anyone of you that had this problem? what I want to know is if there could be any issue relate to this bug. [...] read more
I'm using GNUEABI to remote debug an ARM device, I'm able to set breakpoints, step, view memory, etc. ...in general life is good however when break arbitrarily and then type 'info threads' I do get a list of threads, but the symbols arent resolving for example (gdb) info threads 7 [...] read more
First of all, let me tell you the context. I'm solving problems of the wargame called The lord of the BoF, which is based on RedHat Linux 6.2, which has no address space layout randomization(ASLR), NX bit, ASCII armor, etc.. And the gcc there does not make any dummy when [...] read more
I'm trying to make a truly minimal shared "library" that has the least possible size it can be: .text .globl test test: movb $1, %al movb $1, %dil movabs $message, %rsi movb $7, %dl syscall ret message: .ascii "hello" compiling with: gcc -o test.so -fPIC -shared -m64 -nostdlib -s -O3 [...] read more