# Breakpoint Published articles for Breakpoint. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The case of the progress callback that never got called when progress happened DevFeed: [The case of the progress callback that never got called when progress happened]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-03T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [debugging](), [C#](), [debug](), [Code]() Tags: [breakpoint](), [c-plus-plus](), [c-sharp](), [code](), [debugging](), [handler](), [old-new-thing](), [providers]() ### AI overview A progress callback is never invoked because an intermediary method returns its own operation without forwarding progress reports from the provider's underlying operation. The suggested fix is to return the provider's operation directly so callers can attach to its progress. ### Source excerpt Are you talking to the right guy? The post The case of the progress callback that never got called when progress happened appeared first on The Old New Thing. ## Solana Breakpoint 2026 to take place in London with focus on tokenized markets DevFeed: [Solana Breakpoint 2026 to take place in London with focus on tokenized markets]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-08-27T04:15:00Z Content type: release Language: en Sources: [Solana News Feed]() Topics: [Solana]() Tags: [2026](), [ai](), [announcements](), [blockchain](), [blockchain-technology](), [breakpoint](), [crypto-news](), [cryptocurrency](), [defi](), [events](), [finance](), [london](), [nfts](), [payments](), [podcasts](), [solana](), [solana-ecosystem](), [stablecoins](), [web3]() ### AI overview Solana Breakpoint 2026 will take place in London from November 15-17, bringing together more than 8,000 expected attendees from capital markets, payments, technology and policy. The event will focus on stablecoins, tokenized assets, payments and AI-driven economic activity moving onchain. ### Source excerpt Breakpoint comes to London November 15-17, bringing 8,000+ attendees and leaders from capital markets, payments, technology and policy. ## Breakpoint 2026: Highlights from Day 3 DevFeed: [Breakpoint 2026: Highlights from Day 3]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-06-02T13:03:05Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [AI Agent](), [Model Context Protocol](), [Test automation](), [MCP](), [LangChain](), [observability](), [Retrieval Augmented Generation (RAG)](), [Playwright](), [Cypress](), [debugging](), [Selenium]() Tags: [2026](), [agent](), [ai](), [automation](), [breakpoint](), [ci-cd](), [debugging](), [github](), [github-copilot](), [langchain](), [mcp](), [model-context-protocol](), [observability](), [qa](), [rag](), [testing](), [vscode]() ### AI overview A recap of Breakpoint 2026 Day 3 covering practical masterclasses and lightning talks on AI-driven test generation, non-deterministic testing, MCP-powered QA workflows, automated AI evaluation, and production testing practices. ### Source excerpt All sessions, masterclasses, and lightning talks from Breakpoint 2026 Day 3, covering AI agent testing, test automation with LangChain and CrewAI, MCP-powered QA workflows, Playwright network interception, non-deterministic testing, and building production-grade AI systems. ## Breakpoint 2026: Highlights from Day 2 DevFeed: [Breakpoint 2026: Highlights from Day 2]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-06-01T11:42:52Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Artificial Intelligence](), [Testing](), [Software Testing](), [Software Engineering](), [API]() Tags: [2026](), [ai](), [api-testing](), [breakpoint](), [generative-ai](), [llms](), [qa](), [testing]() ### AI overview This article highlights Day 2 of Breakpoint 2026, focusing on evidence-based discussions of AI-native quality engineering, enterprise AI testing, the future of test engineering, changing QA practices, and human factors in evolving testing roles. Sessions address enterprise AI security and scalability, generative AI, self-healing systems, LLM limitations, and organizational approaches to sustaining quality while increasing delivery speed. ### Source excerpt Explore all sessions, speaker talks, and announcements from Breakpoint 2026 Day 2, covering AI in software testing, the future of test engineering, human-AI collaboration in QA, API testing with AI code assistants, accessibility, and sustaining quality in AI-driven systems. ## Breakpoint 2026: Highlights from Day 1 DevFeed: [Breakpoint 2026: Highlights from Day 1]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-06-01T09:25:38Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Software Testing](), [Testing](), [Artificial Intelligence](), [Test automation](), [Automation](), [API](), [Security](), [prompt injection](), [code productivity](), [Accessibility]() Tags: [2026](), [ai](), [automation](), [breakpoint](), [developer-productivity](), [prompt-injection](), [qa](), [security](), [software-testing](), [testing]() ### AI overview Breakpoint 2026 Day 1 examines how AI-native quality engineering can reduce the traditional trade-off between testing speed and quality. It covers AI-assisted test execution, Copilot-driven automation, intent-based workflows, agentic QA systems, and frameworks for testing AI agents across reasoning, actions, and end-to-end outcomes. ### Source excerpt Explore the biggest announcements, expert insights, and conversations from Breakpoint 2026 Day 1, covering AI in software testing, test automation, developer productivity, accessibility testing, and the future of intelligent testing workflows. ## On-Device Debugging And JUnit 5 DevFeed: [On-Device Debugging And JUnit 5]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-30T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [debugging](), [IntelliJ IDEA](), [Android](), [iOS](), [ide](), [simulator](), [Tooling](), [Code](), [Emulator](), [SDK](), [Visual Studio Code]() Tags: [android](), [android-apps](), [android-studio](), [apk](), [app](), [breakpoint](), [build](), [code](), [debugging](), [developer](), [emulator](), [ide](), [intellij](), [intellij-idea](), [ios](), [java](), [junit](), [linux](), [on-device](), [simulator]() ### AI overview This tutorial describes Codename One's new JDWP-based on-device debugging for ParparVM iOS and Android apps. It explains debugging Java code and objects on simulators and physical devices using IntelliJ IDEA or other JDWP-speaking debuggers, and briefly covers standard JUnit 5 integration with the JavaSE simulator. ### Source excerpt A walk-through of the new JDWP-based on-device debugging pipeline for ParparVM iOS apps and Android apps, with a step-by-step IntelliJ tutorial for each, and a short tutorial on the new standard JUnit 5 integration against the JavaSE simulator. ## Breakpoint 2026 Speaker Spotlight: Andrew Knight DevFeed: [Breakpoint 2026 Speaker Spotlight: Andrew Knight]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-05-08T10:14:54Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Software Testing](), [Artificial Intelligence](), [Behavior-driven development](), [Automation](), [Selenium](), [Playwright](), [MCP Server](), [Open Source]() Tags: [2026](), [ai](), [automation](), [breakpoint](), [breakpoint-spotlight](), [browser](), [enterprise](), [mcp](), [mcp-server](), [open-source](), [qa](), [quality-engineering](), [selenium](), [software](), [software-testing](), [test-coverage](), [testing](), [webdriver]() ### AI overview This speaker spotlight discusses how Andrew Knight combines open-source advocacy with enterprise software testing. It focuses on AI-powered test generation, behavior-driven development, context engineering, human oversight, and tools such as Selenium WebDriver, Playwright AI tooling, CLI skills, and an MCP server. ### Source excerpt Explore how Andrew Knight is using AI, behavior-driven development, and context engineering to reshape enterprise software testing at BrowserStack Breakpoint 2026. This speaker spotlight dives into AI-powered QA, test automation, and the future of modern quality engineering. ## Debugging with ESP-IDF VS Code extension: Part 2 DevFeed: [Debugging with ESP-IDF VS Code extension: Part 2]() Original publisher: [Read original article]() Author: John Lee Published: 2025-06-12T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [VS Code Extension](), [debugging](), [Visual Studio Code](), [Espressif](), [Embedded Software Dev](), [ide]() Tags: [blog](), [breakpoint](), [debugger](), [debugging](), [esp-idf](), [esp32-c3](), [esp32-s3](), [espressif](), [extension](), [gdb](), [jtag](), [tutorial](), [vs-code](), [vscode]() ### AI overview Part two of a guide to debugging Espressif firmware in VS Code with the ESP-IDF extension. It covers launching a debugging session, setting breakpoints, navigating through code, and inspecting variables using gdb and JTAG. ### Source excerpt This two-part guide shows how to set up VS Code with the ESP-IDF extension to debug Espressif boards using JTAG. In this second part, we will debug a simple project using gdb through Espressif's VSCode extension. We will explore the debugging options for navigating the code and inspecting the variables. ## Writing a Debugger From Scratch - DbgRs Part 5 - Breakpoints DevFeed: [Writing a Debugger From Scratch - DbgRs Part 5 - Breakpoints]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2023-09-27T05:28:40Z Content type: tutorial Language: en Sources: [TimDbg]() Topics: [debugging](), [debug](), [Code](), [Windows]() Tags: [breakpoint](), [code](), [debug](), [debugger](), [github]() ### AI overview This tutorial continues the DbgRs debugger series by adding hardware breakpoint support. It also describes cleanup of the Windows debug-event handling, symbol name evaluation, and breakpoint state management. ### Source excerpt (New to this series? Consider starting from part 1) At the end of the last post, we started to get some interesting functionality with the ability to resolve addresses to names in a module. This was the last functionality missing before we could implement breakpoints! This part adds the ability for DbgRs to set hardware breakpoints. The code for this post is in the part5 branch on github. You can also view the changes from part4. ## Time-travel debugging production code DevFeed: [Time-travel debugging production code]() Original publisher: [Read original article]() Author: Loren Sands-Ramshaw Published: 2023-08-07T15:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [debugging](), [debug](), [Code](), [Tooling]() Tags: [breakpoint](), [code](), [debugging](), [history](), [implementation](), [state](), [temporal-concepts](), [time-travel-debugging](), [variables]() ### AI overview This post explains time-travel debugging, also known as reverse debugging, and how it lets developers inspect past program states by stepping backward through execution. It covers the technique's history, examples across languages and development environments, and three implementation approaches, including record and replay. ### Source excerpt Learn how time-travel debuggers, including Temporal, can help you rewind and debug past executions to resolve complex issues efficiently. ## Weird things I learned while writing an x86 emulator DevFeed: [Weird things I learned while writing an x86 emulator]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2023-02-02T07:54:20Z Content type: article Language: en Sources: [TimDbg]() Topics: [Emulator](), [x86](), [Assembly](), [cpu](), [Encoding](), [debugging](), [C++](), [execution]() Tags: [assembly](), [breakpoint](), [c-plus-plus](), [code](), [compilers](), [cpu](), [debugging](), [emulator](), [encoding](), [execution](), [software](), [time-travel-debugging](), [x86]() ### AI overview The author shares x86 and amd64 encoding trivia learned while writing a CPU emulator for Time Travel Debugging. The article explains why alternate instruction encodings matter for software breakpoints, code size, compiler behavior, and CPU understanding. ### Source excerpt If you've read my first post about assembly language, you might expect that this is another post on how to understand assembly language. I will write more about that at some point, but this post is not that. Instead, this post is going to talk about some of the weird things and random trivia I learned while writing an x86 and amd64 emulator. The emulator I wrote was for Time Travel Debugging. ## In-Process Patchless AMSI Bypass DevFeed: [In-Process Patchless AMSI Bypass]() Original publisher: [Read original article]() Author: CCob Published: 2022-04-17T16:30:25Z Content type: tutorial Language: en Sources: [Ethical Chaos]() Topics: [Windows](), [Exception](), [exceptions](), [debug](), [C2](), [Processes]() Tags: [article](), [breakpoint](), [bypass](), [c2](), [context](), [debugger](), [edr](), [exception](), [exception-handling](), [execution](), [extension](), [windows]() ### AI overview This article explains an in-process, patchless AMSI bypass approach using vectored exception handling. It contrasts this technique with SharpBlock's debugger-based child-process method and describes manipulating thread context at the point an exception occurs. ### Source excerpt Some of you may remember my patchless AMSI bypass article and how it was used inside SharpBlock to bypass AMSI on the child process that SharpBlock spawns. This is all well a good when up against client environments that are not too sensitive to the fork and run post exploitation model of operating. What about [...] The post In-Process Patchless AMSI Bypass appeared first on Ethical Chaos. ## Why Isn't X a Hook? DevFeed: [Why Isn't X a Hook?]() Original publisher: [Read original article]() Published: 2019-01-26T00:00:00Z Content type: tutorial Language: en Sources: [Dan Abramov]() Topics: [React](), [React Hooks](), [debugging]() Tags: [article](), [breakpoint](), [bug](), [debugging](), [deep-dive](), [react](), [react-hooks]() ### AI overview This deep dive explains why some React APIs should not be designed as Hooks. It focuses on preserving composition and debugging as applications and custom Hook nesting grow. ### Source excerpt Just because we can, doesn't mean we should. ## Adventures in Production Rails Debugging DevFeed: [Adventures in Production Rails Debugging]() Original publisher: [Read original article]() Author: Scott Francis Published: 2016-03-08T15:43:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Rails](), [debugging](), [Ruby](), [Regular expression](), [ASCII](), [Shopify]() Tags: [ascii](), [breakpoint](), [debugging](), [gdb](), [instrumentation](), [process](), [rails](), [ruby]() ### AI overview This Shopify Engineering article explains how to debug production Rails problems with gdb. It describes retrieving a Ruby call stack, inspecting environment variables, and investigating a warning caused by matching an ASCII regular expression against a UTF-8 string. The approach attaches to an idle Unicorn worker, sets a breakpoint, resumes the process, dumps a core file, and examines the problem out of band without disrupting the customer request. ### Source excerpt 5 minute read At Shopify we frequently need to debug production Rails problems. Adding extra debugging code takes time to write and deploy, so we've learned how to use tools like gdb and rbtrace to quickly track down these issues. In this post, we'll explain how to use gdb to retrieve a Ruby call stack, inspect environment variables, and debug a really odd warning message in production. We recently ran into an issue where we were seeing a large number of similar warning messages spamming our log files: /artifacts/ruby/2.1.0/gems/rack-1.6.4/lib/rack/utils.rb:92: warning: regexp match /.../n against to UTF-8 string This means we are trying to match an ASCII regular expression on a UTF-8 source string. ## Unexpected bug cascade - or how seemingly missing bugs in MSVC builds reveal actual bugs DevFeed: [Unexpected bug cascade - or how seemingly missing bugs in MSVC builds reveal actual bugs]() Original publisher: [Read original article]() Published: 2015-12-27T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [bug](), [MSVC](), [gcc](), [Code](), [function](), [ide](), [export]() Tags: [breakpoint](), [bug](), [code](), [crash](), [export](), [free](), [function](), [gcc](), [msvc](), [null](), [open-source](), [os](), [point](), [react](), [reactos](), [win32](), [winapi]() ### AI overview This article examines how different MSVC and GCC builds exposed a cascade of bugs while investigating a crash in wget.exe. It covers KDBG breakpoint and single-stepping behavior, an MSVC export-resolution issue involving msvcrt.dll and libntdll, and a crash caused by passing a NULL buffer after _vsnprintf returned -1. ### Source excerpt I was looking into CORE-9105, a crash in wget.exe, but I couldn't reproducde it, so I asked Daniel whether he was using an MSVC build or a GCC build. He used a GCC build and I was using an MSVC build. So I tried with a GCC build and the bug appeared. So I looked at this thing with kdbg. And there the first bug showed up. Bug #1: KDBG and break points I set a breakpoint at a position that I wanted to step through and KDBG stopped there. ## A Minimal LLDB Guide for Investigating Crashes DevFeed: [A Minimal LLDB Guide for Investigating Crashes]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2014-06-23T00:00:00Z Content type: tutorial Language: en Sources: [Monica Dinculescu]() Topics: [debugging](), [Tooling](), [clang](), [gdb](), [Chromium]() Tags: [breakpoint](), [chromium](), [clang](), [commands](), [crash](), [debugging](), [gdb](), [tutorials]() ### AI overview A concise tutorial on using LLDB to investigate program crashes. It covers launching an executable, reproducing a crash, reading a stack trace, and setting breakpoints, with Chromium debugging examples. ### Source excerpt lldb stands for Llama-DB, and is a database of llamas you can use to debug programs compiled with clang (lldb is to clang like gdb is to gcc). If you already know how to use gdb, then here's a translation of the common commands. Disclaimer: There is a ton of tutorials and pages about all of the awesome features and commands of lldb, and how to become a debugging pro. This is not that. This is the smallest set of things you need to read to answer the question "what's making this shit crash". That's it. Step 1. Make it go If you want to pass a bunch of arguments to your executable moose, use (´ ▽｀).。ｏ♡ src on fix/moose-crash ☀ ❥ lldb -- moose arg1 arg2 Current executable set to 'moose' (x86_64). If you don't have arguments, lldb foo is enough. This just tells lldb which executable to care about, but it won't actually start the process for you. (lldb) run --> Start or re-start your process (lldb) exit --> Stop your process. Step 2. Make it crash Since we (me) are investigating a crash, the first thing you need is a stack trace that tells you where the crash is. So, start your process in lldb, make it crash, and we'll take it from there. Side bar: I literally typed this blog out while sorting out a crash in the sign-in bits of Chromium, so all my screenshots are Chromium code. Do not panic. Your code can crash just as well if you give it enough time and attention. Once you hit your crash, lldb tells you something like this. I can't tell you how excited I am at that little arrow. It almost looks non-intimidating. Almost. Step 3. Breakpoints! It's hammer time The first thing I did was set a breakpoint at that line to figure out what's going on right before things got crashy (because I'm sure you're dying to know, my crash was happening because we hit that DCHECK which reads "the item should always be signed in" and, spoilers, it isn't) To set a breakpoint in a file at a specific line: (lldb) breakpoint set --file profile_chooser_controller.mm --line 1509 Awesome discovery ## Pinpointing heap-related issues: OllyDbg2 off-by-one story DevFeed: [Pinpointing heap-related issues: OllyDbg2 off-by-one story]() Original publisher: [Read original article]() Author: Axel "0vercl0k" Souchet Published: 2013-09-09T16:53:00Z Content type: tutorial Language: en Sources: [Diary of a reverse-engineer]() Topics: [debug](), [bug](), [Assembly](), [x86](), [App]() Tags: [assembly](), [breakpoint](), [bug](), [crashes](), [debug](), [debugger](), [debugging](), [heap](), [reverse-engineering](), [x86]() ### AI overview A technical walkthrough of diagnosing an off-by-one heap-related crash in OllyDbg2. The article uses GFlags, PageHeap, and WinDbg to locate the fault and reverse-engineer the buggy code and a reproducible trigger. ### Source excerpt Introduction Yesterday afternoon, I was peacefully coding some stuff you know but I couldn't make my code working. As usual, in those type of situations you fire up your debugger in order to understand what is going on under the hood. That was a bit weird, to give you a ... ## Breakpoints in gdb using int3 DevFeed: [Breakpoints in gdb using int3]() Original publisher: [Read original article]() Author: Mark Seaborn (noreply@blogger.com) Published: 2010-05-01T11:59:00Z Content type: tutorial Language: en Sources: [Mark Seaborn]() Topics: [debugging](), [Assembly](), [x86](), [Linux](), [Ubuntu]() Tags: [assembly](), [breakpoint](), [debugging](), [debugging-tools](), [gdb](), [glibc](), [linux](), [memory](), [signal](), [x86](), [x86-64]() ### AI overview This article explains how inserting the x86 int3 instruction, for example through __asm__("int3"), can trigger a breakpoint while debugging with gdb. It notes that int3 raises SIGTRAP, allowing inspection of registers, memory, and the call stack under gdb, and can be useful when setting a source-line breakpoint is impractical, such as within inline assembly. ### Source excerpt Here is a useful trick I discovered recently while debugging some changes to the seccomp sandbox. To trigger a breakpoint on x86, just do: __asm__("int3"); Then it is possible to inspect registers, memory, the call stack, etc. in gdb, without having to get gdb to set a breakpoint. The instruction triggers a SIGTRAP, so if the process is not running under gdb and has no signal handler for SIGTRAP, the process will die. This technique seems to be fairly well known, although it's not mentioned in the gdb documentation. int3 is the instruction that gdb uses internally for setting breakpoints. Sometimes it's easier to insert an int3 and rebuild than get gdb to set a breakpoint. For example, setting a gdb breakpoint on a line won't work in the middle of a chunk of inline assembly. My expectations of gdb are pretty low these days. When I try to use it to debug something low level, it often doesn't work, which is why I have been motivated to hack together my own debugging tools in the past. For example, if I run gdb on the glibc dynamic linker (ld.so) on Ubuntu Hardy or Karmic, it gives: $ gdb /lib/ld-linux-x86-64.so.2 ... (gdb) run Starting program: /lib/ld-linux-x86-64.so.2 Cannot access memory at address 0x21ec88 (gdb) So it's nice to find a case where I can get some useful information out of gdb.