0 views collected around this technical thread.
This comprehensive guide explains what Linux kernel Oops errors are, why they occur, and provides step‑by‑step debugging techniques—including environment setup, kernel configuration, printk usage, BUG macros, GDB, objdump, and memory‑checking tools—to help developers quickly locate and fix Oops issues in custom kernel modules.
This article explains how to troubleshoot and resolve the MySQL "Too many connections" error by using GDB to modify the max_connections parameter on a running MySQL 5.7 instance without restarting, including step‑by‑step commands, sysbench load testing, and two practical methods.
This article provides an in-depth tutorial on the GNU Debugger (GDB), covering its purpose, installation, basic and advanced commands, remote debugging, memory analysis, and practical tips for efficiently debugging C/C++ applications on Linux and Windows platforms.
This article explains how to set hardware and software watchpoints in GDB to monitor specific memory addresses, demonstrates the technique with a multithreaded C++ example, and describes the underlying CPU debug registers that enable precise detection of reads and writes.
This article explains what memory out-of-bounds errors are, why they are dangerous in Linux C programs, and provides step‑by‑step debugging methods using logs, GDB, Valgrind, core dumps, mprotect, static analysis, and preventive coding practices.
This article explains Linux core dump generation, common causes such as null pointer dereference and array overflow, configuration steps, and demonstrates how to analyze core files using GDB with practical code examples and multi‑threaded case studies.
This article explains how to locate OBServer crash logs, extract stack traces from observer.log, map memory addresses to source code using addr2line and gdb, identify the faulty function ObMPStmtExecute::copy_or_convert_str, and verify the issue through the OceanBase knowledge base, providing a systematic five‑step approach for rapid crash diagnosis.
This article provides a thorough introduction to the GNU Debugger (GDB), covering its core capabilities, startup methods, compilation requirements, a wide range of debugging techniques—including breakpoints, memory inspection, disassembly, reverse execution—and detailed guidance for multithreaded debugging on Linux systems.
This article introduces CGDB, explains how to choose the appropriate GDB version, provides step‑by‑step installation commands for both CGDB and GDB, and demonstrates practical debugging scenarios with MySQL, including attaching to processes, inspecting threads, analyzing core dumps, and adjusting runtime variables.
This article provides a comprehensive guide on how to employ GDB for debugging programs that lack symbol information, covering basic commands, breakpoint techniques, core‑dump analysis, reverse debugging, and a practical example of integrating VSCode, GDB, and QEMU to debug an ARM64 Linux kernel.
The article analyzes a MySQL 5.7 replication bug where, after consecutive crashes, the slave ends up with more GTIDs than the master because the last binlog’s GTIDs are not persisted, and demonstrates the problem using GDB debugging and step‑by‑step reproduction.
This article walks through C++ object memory layout using concrete examples, covering basic data members, methods, private and static members, inheritance (with and without virtual functions), compiler optimizations, and address‑space layout randomization, all demonstrated with GDB inspections and code snippets.
An amusing yet instructive narrative shows how a C program that crashes with a segmentation fault can appear to work after inserting a printf, explaining that uninitialized local variables contain leftover stack data and that debugging tools like GDB reveal the true cause.
The article analyzes how private keys for workloads uploaded via Istio Ingress gateways can be exposed in plaintext, stored in memory, and extracted using tools like OpenSSL and GDB, and discusses mitigation strategies such as Intel SGX‑based protection.
This article explains how C++ implements runtime polymorphism through virtual function tables, analyzes the memory layout of single‑ and multiple‑inheritance classes using gcc and gdb, and clarifies the role of thunks and offset adjustments for correct virtual calls.
This article provides a comprehensive, step‑by‑step tutorial on setting up a local VSCode environment, configuring remote GDB, building and deploying the OceanBase observer, and performing source‑level debugging of the observer binary on Linux servers.
This article explains how to use GDB watchpoints to monitor specific memory locations in C/C++ programs, demonstrates setting hardware watchpoints, shows example code with a thread modifying a variable, and details the underlying CPU debug registers that enable real‑time detection of memory reads and writes.
The article introduces Alibaba Cloud's Graph Database (GDB), detailing its product features, supported query languages, high‑performance and high‑availability architecture, parallel execution engine based on the Volcano model and Morsel‑driven parallelism, and showcases real‑world use cases such as DingTalk friend recommendation and Hema Fresh recommendation.
The article explains how to integrate Alibaba's Graph Database (GDB) with TinkerPop, compares it to other graph databases, details challenges such as string‑based script construction and missing transaction APIs, and demonstrates two DAO implementations and explicit transaction handling using GdbClient.
This article explains what program core dumps are, how to interpret core‑dump files, and provides detailed GDB debugging techniques—including register inspection, stack frame analysis, variable printing, memory dumping, and handling optimized code—to locate and resolve the root causes of crashes.