Mar 5, 2012 · 85 Basically, I want to get typeid(*this).name(), i.e. the real type of this. I want to get this in GDB (without modifying the source code). I tried print typeid(*this) but it says that typeid is unknown …

Nov 23, 2025 · When debugging C++ code—especially with polymorphism—understanding the **real (dynamic) type** of the `this` pointer is often critical. Consider a scenario where a base class pointer …

get_basic_type (type) Return type with const and volatile qualifiers stripped, and with typedefs and C ++ references converted to the underlying type. C ++ example: typedef const int const_int; const_int foo …

You can turn to the source code to seek this out. If the type turns out to be a struct/class, typedef, or type alias, you might need to do a bit more spelunking to fully understand what kind of data is in play. …

4 days ago · Without this info, GDB assumes it might be dangerous to execute, so it triggers that "unknown return type" warning. Instead of casting every time, the "clean" way to fix this is to make …

Jul 1, 2016 · gdb does not find any matching in the source for type 'mytype'. But if I remove comment in line 12, gdb finds the type definition and outputs this:

Oct 24, 2008 · Sometimes gdb prints "incomplete type" for some type of variables. What does this mean and how can we see that value?

Dec 12, 2025 · 7. Conclusion Incomplete type errors in GDB stem from missing type metadata in debug symbols. By understanding why these errors occur—GDB’s reliance on type layout information—you …