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.
I'm on Windows 7 64bit, using VS2013 Express for Desktop. Compile as default (using SSE) D:\Work>cl printf-test.c Microsoft (R) C/C++ Optimizing Compiler Version 18.00.21005.1 for x86 D:\Work>printf-test.exe FPU control word 0x0000037f 0. FPU status 0x00000000 1. 0x43380000 0x00000000 1. FPU status 0x00000000 2. 0x43380000 0x00000001 2. FPU status 0x00000000 3. [...] 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