Source code Analysis Layout |——————————–| | vector vec | | 1 | 2 | 3 | 4 | 5 |
Continue readingCategory: Debugging & Memory
Unwind the stack even if GDB can’t? (ARM)
Reason Since GCC 5.0 for ARM the default used ABI is AAPCS1. With AAPCS the stack unwinding works based on
Continue readingAnalysing more complex data types (GDB)
Code Analysis Info: The used version of Python Pretty-Printer (used by GDB) couldn’t handle ‘print pastries’.
Continue readingProblems happening with multithreading (C++)
The two most common problems that are happing when dealing with multithreading are the deadlock and the race condition. Follow
Continue readingCommon reasons for program crashes (C++)
1. Illegal memory access 2. Allocating to much memory 3. Unsolved error handling
Continue readingRemote debugging (gdbserver)
Remote debugging creates the possibility to debug applications on a remote device. Host system (gdb) Target system (gdbserver) Precondition Installed
Continue readingMemory Management (Basics)
Process Each process is running on its own virtual address space. The MMU does the necessary translation from/to the physical
Continue readingCoredump analysis (GDB)
Setup Details ▼ Activate cordumps for the current session Set coredump size to unlimited Set pattern to store coredump Threads
Continue readingMemory Management (C++)
1. Automatic allocation – Stack Objects created on the stack, will be cleaned up automatically after they have run out
Continue reading