Here's a practical, minimal guide for using GDB in Ubuntu terminal — from launching to setting breakpoints and navigating your code. 🧰 Step 1: Compile with Debug Symbols Use -g and disable optimizations ( -O0 preferred for debugging): bash Copy Edit g++ -g -O0 -o myprog myprog.cpp 🚀 Step 2: Launch GDB bash Copy Edit gdb ./myprog You'll see a (gdb) prompt. 🎯 Step 3: Set Breakpoints You can set breakpoints in three main ways : ✅ a. At a function gdb Copy Edit (gdb) break main ✅ b. At a specific file and line gdb Copy Edit (gdb) break myprog.cpp:42 ✅ c. At a method in a class gdb Copy Edit (gdb) break MyClass::doSomething If the symbol is mangled (C++), GDB usually demangles automatically, especially if compiled with -g . ▶️ Step 4: Run the Program gdb Copy Edit (gdb) run 🧠Step 5: Navigate Command Meaning next or n Step over current line step or s Step into function call finish Run until current function returns continue or c Continue until...
Ubuntu Notes: Solve E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem when trying to update ubuntu
This the problem you face when you try to upgrade or update ubuntu using command line, you get this message.
Again when you run 'sudo dpkg --configure -a' command you get error message like
dpkg: error: parsing file '/var/lib/dpkg/updates/0019' near line 0:
newline in field name '#padding'
---
To solve this run command as follows
cd /var/lib/dpkg/updates && sudo rm -rf <refNo>;
sudo dpkg --configure -a;
Like in above question case run command as follows
cd /var/lib/dpkg/updates && sudo rm -rf 0019;
sudo dpkg --configure -a;
==
Thats all & problem will be solved
Comments
Post a Comment
If you have any doubts, please let me know.