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 working on small Windows Exception handling engine trying to gather maximum information from the system, including C++ exceptions RTTI. In a 32-bit VectoredExceptionHandler compiled by MSVS 2015, I successfully can obtain std::type_info pointer to RTTI of the type being thrown. It can easily be found in ((_ThrowInfo*) ExceptionPointers->ExceptionRecord->ExceptionInformation[2])->pCatchableTypeArray->arrayOfCatchableTypes[0] (see [...] read more
I've only started getting this problem recently, and I have no idea when it started occuring/what causes it. I have this simple test program here: #include <iostream> int main() { return 0; } but when I try to run it normally, it creates a stackdump. Stack trace: Frame Function Args [...] read more
A comment more than a question: The following describes an issue I had this evening and what I did to "correct" it. These events required a few hours of time to resolve. As this site is one of my favorite sources of information, thought this post might benefit someone else. [...] read more
my.cpp: #include<stdio.h> int main() { printf("hello main"); return 0; } build with gcc and then i use gdb to run the program, error occurred. gdb: unknown target exception 0x406d1388 at 0x75fca6f2 Program received signal ?, Unknown signal. 0x75fca6f2 in RaiseException () from /cygdrive/c/WINDOWS/System32/KERNELBASE.dll gcc info: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/5.4.0/lto-wrapper.exe [...] read more
When trying to run a program using gdb I get [New Thread 4612.0x158c] [New Thread 4612.0x1cb8] [New Thread 4612.0x11e8] [New Thread 4612.0x1190] gdb: unknown target exception 0x406d1388 at 0x746623d2 Program received signal ?, Unknown signal. 0x746623d2 in RaiseException () from /cygdrive/c/WINDOWS/System32/KERNELBASE.dll I researched this and found three possible causes: (1) [...] read more
I am using the suggested way to set the name of a thread via SetThreadName. It works, and I see the names changing in the thread view tool window. However, I frequently get an exception message printed out to the debug output window. Since I have several threads, I may [...] read more
The Microsoft-approved way of setting a thread name doesn't compile with /EHsc enabled. The compiler tells me C2712: Cannot use __try in functions that require object unwinding http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx // // Usage: SetThreadName (-1, "MainThread"); // typedef struct tagTHREADNAME_INFO { DWORD dwType; // must be 0x1000 LPCSTR szName; // pointer to [...] read more
I'm using the following code (from MSDN) to rename a C++ thread: #include <windows.h> const DWORD MS_VC_EXCEPTION=0x406D1388; #pragma pack(push,8) typedef struct tagTHREADNAME_INFO { DWORD dwType; // Must be 0x1000. LPCSTR szName; // Pointer to name (in user addr space). DWORD dwThreadID; // Thread ID (-1=caller thread). DWORD dwFlags; // Reserved [...] read more
I am trying to run a very simple hello world for SDL. if I execute the program using 'run' it works fine but when I use 'debug' GDB complains about receiving signal ?. Not really sure what I am doing wrong here... I am also new to CLion main.cpp #include [...] read more
I was "messing" with threadpools and I noticed a strange exception. So I'm here to ask you: am i using this object correctly? Or you think it is just a bug or a dummy warning? Here it is. I implemented a basic example with QThreadPool (it's almost the same as [...] read more
I am experiencing problems with phonon direct show backend on WinXP. Basically it doesn't work at all for me I've tried it with both 4.7.0 SDK and with version built from sources. In both cases phonon_ds94.dll is located in /plugins/phonon_backend/ dir. My system is WinXP and I use VS 2008. [...] read more