Explore >> Select a destination
|
You are here 
|
www.humprog.org | ||
| | | | |
werat.dev
|
|
| | | | | Conditional breakpoints are extremely useful, but everyone knows [citation needed] that they're super slow, to the point where people stop using them. Visual Studio recently did some good improvements and @ryanjfleury still dunked on it for being too slow. But even raddbg takes ~2 seconds to execute 10000 iterations of a simple loop with conditional breakpoints inside. For comparison, the same loop without breakpoints takes less than 1ms. So why is it so damn slow? Let's explore how conditional breakpoints are typically implemented in modern debuggers, where the performance problems come from and what can be done to make things go fast. | |
| | | | |
riv.dev
|
|
| | | | | How to write a CHIP-8 emulator. | |
| | | | |
www.timdbg.com
|
|
| | | | | [AI summary] This article provides an introduction to reading x86 assembly language, emphasizing its importance for understanding how programs operate at a fundamental level. It covers the basics of assembly syntax, common instructions, and practical tools for reading and analyzing assembly code. The author explains that while assembly is often viewed as complex, it's actually more approachable than many believe, especially for debugging and reverse engineering tasks. The article also highlights the differences between Intel and AT&T syntax, the structure of assembly instructions, and the role of registers and memory addressing in x86 architecture. | |
| | | | |
justanotherdot.com
|
|
| | | the blog of Ryan James Spencer | ||
