Hizenberg/GDB-tutorial
1
0
Fork 0
mirror of https://github.com/Hizenberg469/GDB-tutorial.git synced 2026-04-19 22:02:23 +03:00
Code Issues Packages Projects Releases Wiki Activity

process stack done - debugging technique begins

Browse Source
This commit is contained in:
Hizenberg
2025-10-19 09:41:53 +00:00
parent 2c7823e97a
commit dde42f2bac
2 changed files with 59 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
debugging-techniques.txt Normal file
View File

@@ -0,0 +1,5 @@
DEBUGGING TECHNIQUES:
---------------------

54
process-stack.txt
View File

@@ -131,3 +131,57 @@ Section 7: Foundation of Processes (Part A):
We can also use Address-sanitizers
* Stack Overflow:
~~~~~~~~~~~~~~~
When the size of any number of call stack crosses the
finite size of the allocated stack of the program, then
it leads to stack overflow.
+---------------------------+
| |
| stack | |
|---------------------------| |
| | |
| array[0] | |
| array[1] | |
| | | |
| | | |
| | | \|/
| | | *
| array[99....] |
|---------------------------|
| array[10....0] |
| heap |
| |
|---------------------------|
| |
| data |
| |
| |
|---------------------------|
| |
| .text |
| |
+---------------------------+
* Address Sanitizer:
~~~~~~~~~~~~~~~~~~
To know about potential memory leaks, we can enable stanitizer flag
Compiler flag:
-fsanitize=address
* To detect memory leak, we can use valgrind.
Command:
$valgrind --leak-check=full ./<program>
OR
$valgrind ./<program>