How epasveer/seer works
Project type and purpose
• Project type: Desktop GUI application (C++17/Qt6) that serves as a front-end to GDB’s Machine Interface (MI) for Linux.
• Purpose: Provide a user-friendly interface for launching and controlling GDB, visualizing source, assembly, memory, arrays, structs, threads, stack frames, breakpoints, watchpoints, catchpoints, printpoints, and reverse debugging.
File structure
• Top-level directories
• src/ – All C++ source (.cpp/.h), Qt UI definitions (.ui), QRC resource files, and the main entrypoints (seergdb.cpp, seerutl_test.cpp).
• tests/ – Integration and example tests against various languages and platforms (Rpi4, C, Fortran, Ada, CUDA, Rust, etc.).
• debian/, .github/ – Packaging scripts and CI workflows for multiple OS targets.
• notes/, images/ – Design notes and screenshots.
• Key patterns
• Modular Qt widgets for each view (e.g., SeerConsoleWidget, SeerMemoryVisualizerWidget).
• A GdbMonitor class to encapsulate GDB MI interaction.
• Multiple “browser” widgets implementing MVC-style separation:
– Model: QAbstractItemModel subclasses hold data (e.g., SeerBreakpointModel).
– View: Qt widgets (QTreeView, QTextEdit) render data.
– Controller: Slots and commands injected into GdbMonitor.
• CMake build structure with build_seerutl subproject for command-line helper.
README for additional insights
• Confirms dependencies: C++17, Qt6 (Widgets, Charts, Svg, PrintSupport), CMake, GDB MI.
• Describes core UI areas: Code Manager, Variable/Register Info, Breakpoint/Watchpoint/Catchpoint/Printpoint managers, Stack/Thread explorers, Memory/Array/Struct/Image visualizers, Reverse Debugging controls.
• Emphasizes GDB MI protocol as communication channel.
Elements
• Clear labels for each block (component name and role).
• UI → Logic → GdbMonitor → GDB
• GDB → GdbMonitor → Models → UI
• Blue rectangles for UI components.
• Green rectangles for core logic/models.
• Orange ellipse for GdbMonitor / communication layer.
• Use connectors with labels like “MI Request”, “MI Response”, “Signal/Slot”.
Detail
• How QProcess is invoked and stdout parsed.
• Packaging and CI as external processes if relevant.
• Don’t over-aggregate—represent each major feature area as its own component.