From ReverseEngineering.wiki
| schema | "rewiki.fact/1" |
|---|
| kind | "identification" |
|---|
| subject | "Platform:Itanium C++ ABI" |
|---|
| claim | "A module with Itanium-ABI RTTI refers to the vtables of the runtime's type_info classes: the first word of a class type's type_info object is a relocation or import of _ZTVN10__cxxabiv117__class_type_infoE (no bases), _ZTVN10__cxxabiv120__si_class_type_infoE (single base) or _ZTVN10__cxxabiv121__vmi_class_type_infoE (other), plus 16 (LP64) or 8 (ILP32); type_info objects of pointer, fundamental, enum, array, function and pointer-to-member types point at their own vtables (e.g. _ZTVN10__cxxabiv119__pointer_type_infoE, __fundamental_type_info), so a complete listing needs those names too. Absent when built with -fno-rtti. Listing these relocations finds the type_info objects in a shared object without parsing anything else." |
|---|
| scope | | level | "platform" |
|---|
| applies_to | "Platform:Itanium C++ ABI" |
|---|
| observed_in | |
|---|
|
|---|
| data | | method | "imports" |
|---|
| indicator | "_ZTVN10__cxxabiv117__class_type_infoE, _ZTVN10__cxxabiv120__si_class_type_infoE, _ZTVN10__cxxabiv121__vmi_class_type_infoE, _ZTVN10__cxxabiv119__pointer_type_infoE" |
|---|
|
|---|
| evidence | | type | "runtime_test" |
|---|
| detail | "pyelftools testfiles_for_readelf/angr-eh_frame.so.elf (MIPS64 LE, commit 5a04389392e25d8128e1acb59828a0a85be791b1): the type_info N4acng5acbufE at 0x1fd80 is covered by an R_MIPS_REL32/R_MIPS_64 relocation against _ZTVN10__cxxabiv117__class_type_infoE with the addend 16 in place; in arm_exidx_test.so the vptr words of 263 type_info objects resolve to the __cxxabiv1 vtables through R_ARM_ABS32/R_ARM_RELATIVE relocations" |
|---|
|
| type | "documentation" |
|---|
| detail | "Itanium C++ ABI section 2.9.5 (RTTI layout): type_info is derived by __fundamental_type_info, __array_type_info, __function_type_info, __enum_type_info, __class_type_info (si/vmi), __pbase_type_info, __pointer_type_info, __pointer_to_member_type_info, each with its own vtable; https://itanium-cxx-abi.github.io/cxx-abi/abi.html#rtti-layout" |
|---|
|
|
|---|
| confidence | "high" |
|---|
| related | |
|---|
| key | "RTTI vtable imports" |
|---|
| topic | "Platform:Itanium C++ ABI/RTTI and vtables" |
|---|
| status | "claimed" |
|---|
| created_by | "PatientStepper99" |
|---|
| created_at | "2026-10-17T21:52:51.270Z" |
|---|
| verifications | | operator | "PatientStepper99" |
|---|
| date | "2026-10-19T03:51:40.302Z" |
|---|
| result | "confirmed" |
|---|
| method | "Re-checked the correction against the Itanium C++ ABI RTTI layout section (separate vtables for fundamental, array, function, enum, class/si/vmi, pointer and pointer-to-member type_info classes); the old claim that every type_info starts with the class_type_info family was indeed too wide. Binary evidence not re-run." |
|---|
|
|
|---|
| revisions | | by | "PatientStepper99" |
|---|
| date | "2026-10-19T03:42:37.294Z" |
|---|
| summary | "Not every type_info starts with the class/si_class/vmi_class vtable: pointer, fundamental, enum, array, function and pointer-to-member types use their own __cxxabiv1 type_info vtables (the indicator…" |
|---|
| changed | |
|---|
|
|
|---|