Skip to main content
SimilarExport ZIP
100%

Tema 3.1 Compilación CMake y corrida GEF (gdb) del programas

✓ Published0🌍 Public
IIoTeacher
Last edited Apr 15, 2024
Created on Apr 15, 2024

This example documents a terminal session that guides a user through compiling a C program with CMake and debugging it with the GNU debugger (GDB). The material is presented as a markdown file containing step-by-step commands and notes, culminating in the use of `script` and `scriptreplay` utilities to record, claim, and share the interactive terminal session. The text demonstrates the compilation and debugging workflow for a specific project, named LDI-31, while explaining how to finalize the recording, access the playback URL, and distribute the session link to others.

AI-generated description

Similar vizzes

Loading thumbnail…

uso de GIST desde la terminal con $ temux

This visualization demonstrates how to use GitHub CLI from a terminal to create and manage gists, with a focus on integrating `gh` into `tmux` workflows. It shows the process of installing `gh` on Ubuntu Server ARM64 and Termux, authenticating via `gh auth login`, and creating a private gist with `gh gist create`. The example includes a `tmux` configuration that binds custom key sequences (CTRL+1 through CTRL+5) to compile, run, debug, upload, and record assembly code. The code uses shell commands like `as`, `ld`, `gdb`, and `asciinema`, along with the `gh` API for gist creation.

IIoTeacher
64% match
Loading thumbnail…

Para principiantes profesionales de uso shell con $ tmux

This example presents a two-part technical guide for developers using assembly and tmux. The first section walks through compiling, debugging, and versioning ARM64 assembly programs with `gcc`, `gdb`, and `git`, showing a step-by-step command table and code snippets. The second part explains tmux basics like sessions, windows, and panes, with commands such as `C-b c` and `C-b %` to manage them. The text uses plain tables and markdown to organize the workflow for students working on AWS servers.

IIoTeacher
62% match
Loading thumbnail…

GDB cheat sheet

This visualization is a structured reference sheet for GDB commands, organized by function such as startup, breakpoints, running the program, and stack backtrace. It presents terminal-style text entries with syntax highlighting to distinguish commands, arguments, and comments. The layout uses a simple grid-like arrangement derived from the markdown source, rendering each command as a code snippet with its description. The design prioritizes scannability for quick lookup, relying on plain HTML and CSS rather than a charting library.

IIoTeacher
61% match
Loading thumbnail…

Gist e30b580e1eb3c9e76102ba926ac0e85a

This example shows a complete GitHub Classroom activity template in Spanish, guiding students through designing a small thematic practice project using ARM64 Assembly, Bash, Python, or C. It emphasizes documentation-first development, with a structured repository of Markdown templates for proposal, use case, repository structure, and test plans, plus a shell script and source stub. The visualization relies on plain text file rendering via the web interface, illustrating how to scaffold a minimal, well-documented coding assignment without external frameworks or complex dependencies. The code uses no external libraries, focusing instead on repository organization and pedagogical instructions.

IIoTeacher
60% match
Loading thumbnail…

Compiación de ARM Assembly en RaspbianOS

This example shows the compilation and debugging workflow for ARM assembly code on Raspbian OS, using a Mermaid sequence diagram to trace interactions between a developer, text editor, Makefile, GNU Assembler (as), GNU Linker (ld), the system, and GDB with GEF. The diagram documents how the developer writes and saves a `.s` file, adjusts the Makefile, compiles to object code, links an executable, runs it, and invokes GDB for debugging. The visualization renders Mermaid’s `sequenceDiagram` syntax directly, with participant aliases and labeled arrows capturing each step.

IIoTeacher
58% match
Loading thumbnail…

Actividad: Cheat Sheet de ARM32 lenguaje ensamblador con GEMINI

This interactive data visualization is an educational cheat sheet for ARM32 assembly language, created as a GitHub Gist in Markdown. It uses the Gemini AI tool to distill and annotate key sections from a poster by Azeria Labs, organizing information on basic instructions, assembly directives, and addressing modes into a clear, concise reference. The content is structured directly in Markdown syntax, with examples and summaries provided for each topic, and includes a link to the original poster and official ARM documentation for further study.

IIoTeacher
55% match
Loading thumbnail…

Ensamblador SCRIPT de inicialización para AWS ARM nodo para compilar en 64 bits

This example shows a shell script that automates the setup of an AWS Academy ARM64 node for assembly-language compilation in 64-bit mode. It runs `sudo apt-get update` and `apt-get upgrade`, then installs a set of development tools including `build-essential`, `git`, `nano`, `gdb`, `curl`, `tree`, `cmake`, and `protobuf-compiler`. The script actively prints status messages about each package, naming the author and hinting at future changes, while relying on the standard APT package manager to fetch and configure the toolchain.

IIoTeacher
54% match
Loading thumbnail…

Emacs Debugging Workshop

This visualization demonstrates the Emacs debugging workflow through a series of instrumented Lisp examples, showing how the built-in debugger and Edebug interact with source buffers, stack frames, and invocation messages. The buffer uses `lisp-interaction-mode` and defines key bindings for `eval-print-last-sexp`, while examples trigger `debug-on-variable-change`, `debug-on-message`, and `debug-on-error` to pause execution. The code also exercises Edebug’s stepping, tracing via `edebug-trace`, and conditional breaks through `edebug` calls, relying on standard Emacs Lisp functions like `(debug)`, `toggle-debug-on-quit`, and `with-output-to-temp-buffer` to produce backtraces and evaluation control. The source text itself serves as the data, with the rendering being the interactive debugging session.

DDarMontou
54% match