C++ New Added 9 October 2026

C++: error: 'uint8_t' does not name a type

The file uses fixed-width integer types without including <cstdint>, and only ever compiled because another standard header pulled it in indirectly. GCC 13 trimmed those internal includes in libstdc++, so code that built for years breaks on upgrade, often inside a third-party library. The same happens with std::runtime_error without <stdexcept>.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Which compiler started it?
g++ --version

# Include what the file actually uses, at the top of the file
#include <cstdint>     // uint8_t, int64_t
#include <stdexcept>   // std::runtime_error
#include <string>      // std::string

# Other files using the types without the header
grep -rlE '\bu?int(8|16|32|64)_t\b' src/ | xargs grep -L 'cstdint\|stdint.h'

# Third-party code you cannot edit yet: force the include as a stopgap
CXXFLAGS="-include cstdint" cmake -B build

How to diagnose C++ errors

C++ errors fall into two very different worlds. Compile and link errors (undefined reference, multiple definition, template substitution failure) are deterministic and are almost always about declarations, the One Definition Rule, or link order. Runtime memory errors (segfaults, double free, use-after-free) are non-deterministic and should never be debugged by reading code alone; a sanitizer will find in seconds what code review misses for days.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Rebuild with sanitizers before anything else: -fsanitize=address,undefined -fno-omit-frame-pointer -g. AddressSanitizer reports the exact allocation and free sites for use-after-free and double-free.
For undefined-reference errors, check link order, remembering that with GNU ld libraries must come after the objects that use them, and check for a C/C++ linkage mismatch that needs extern "C".
Use nm -C libfoo.a | grep symbol to confirm the symbol is actually present and to see the demangled signature. A signature that differs by a const is a different symbol.
Enable core dumps (ulimit -c unlimited) and open them in gdb with gdb ./binary core, then bt full. A stack trace beats speculation.
For template errors, read the message from the bottom up. The final line is usually the real constraint that failed; everything above is instantiation context.

Tools worth reaching for

-fsanitize=address,undefined
valgrind
gdb / lldb
nm -C
ldd

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

gcc.gnu.org

Related C++ errors

See all 20 C++ errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.