Emacs Debugging Workshop

100%

Emacs Debugging Workshop

✓ Published0🌍 Public

Last edited Jul 3, 2019

Created on Nov 8, 2018

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.

AI-generated description

Similar vizzes

Loading thumbnail…

Elisp Evaluation Workshop

This interactive Emacs Lisp evaluation workshop demonstrates how the language evaluates different forms, from self-evaluating objects like numbers and strings to symbol indirection and function invocation. The buffer pairs source code with explanatory comments, encouraging exploration through `eval-print-last-sexp` bindings like `C-j`. It covers function calls, special forms, macros, quoting, and backquoting, using APIs such as `symbol-function`, `fset`, `funcall`, and `apply`. The example exposes runtime errors, like the wrong-type-argument from `apply`, and includes a commented-out infinite loop, making evaluation behavior concrete and testable.

DDarMontou

73% match

Loading thumbnail…

Gist 154614

This example demonstrates how to build a dynamic, animated data visualization using the Firebug debugger service. The code, written in JavaScript, initializes components through the XPCOM interface and uses the jsdIDebuggerService to interact with JavaScript execution. It processes source code by matching patterns with regular expressions to identify functions and URLs. The visualization uses an animation rendering approach, driven by the underlying Firebug runtime environment, to explore and display code structures in a dynamic way. The data source is the JavaScript files being analyzed for function names and location details.

CCaged

59% match

Loading thumbnail…

run with debugger

This example demonstrates a JavaScript debugging utility called `runWithDebugger`, which invokes a callback function while pausing execution at a `debugger` statement. The code defines multiple test functions, such as `sayHi`, `sayHiTo`, and `sayFullName`, that log messages to the console via `console.log`. The utility handles zero to four arguments by explicitly branching on the length of the supplied arguments array, then calls the callback with the appropriate parameters. The page relies solely on native browser debugging tools and plain JavaScript, with no external libraries or data sources.

深深度碎片

57% match

Loading thumbnail…

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

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.

IIoTeacher

54% match

Loading thumbnail…

List of Workshops

This example visualizes the schedule and topics of a fall 2015 workshop series, using a gist of raw Markdown as its data source. It renders each workshop as a distinct element, likely a card or list item, with titles, instructors, and dates drawn directly from the parsed text. The code employs a custom JavaScript parser to extract session details and uses d3.js for layout and transitions, though the core rendering relies on simple DOM manipulation via `d3.select` and `text` methods. The visualization emphasizes chronological ordering and thematic grouping, though it does not show interactive filtering or dynamic updates beyond static display.

CCliffordAnderson

53% 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

53% match

Loading thumbnail…

D3 Workshop: Part 1 - Basic HTML, d3, and Data Binding

This example demonstrates an interactive D3 v4 workshop that teaches basic HTML, d3, and data binding through a hands-on exercise. It shows a button that, when clicked, runs a d3 code snippet targeting paragraphs inside a sandboxed div, while a checklist outlines tasks like adding paragraphs, manipulating text, and binding arrays. The code uses d3.js v4, with d3.select and d3.selectAll to handle DOM selection and manipulation, plus event handling for button clicks. The visualization renders static HTML paragraphs as the primary data display, with the exercise structure guiding users through progressive coding challenges.

IIgathi

52% match

Loading thumbnail…

warning and error messages when doing quick setup for firefox debugger

This example visualizes the sequence of warning and error messages generated during a Firefox debugger quick setup, drawn from a terminal log in a gist. It tracks the progression of yarn installation, git cloning, and dependency resolution, highlighting peer dependency warnings and a failed fsevents binary download. The visualization uses React to render the log as a structured timeline, with color-coded nodes or bars to distinguish warnings, errors, and successful steps. The rendering approach leverages React’s component-based layout to map each console line to a visual element, emphasizing the mix of npm, node-gyp, and network-related issues encountered.

深深度碎片

52% match