Logging C Function Calls
May 19th, 2022 @ justine's web page Logging C Functions One of my favorite features of the Cosmopolitan Libc runtime is its --ftrace flag that logs C function calls. It's the simplest system for debugging programs I've ever used and it surprises me that I found no evidence of someone having invented it before. Here's one of its most important use cases. Have you ever had you debugger stupified by
Rust on MIPS64 Windows NT 4.0
Introduction Some part of me has always been fascinated with coercing code to run in weird places. I scratch this itch a lot with my security research projects. These often lead me to writing shellcode to run in kernels or embedded hardware, sometimes with the only way being through an existing bug. For those not familiar, shellcode is honestly hard to describe. I don’t know if there’s a very form
âš™ D54604 Automatic variable initialization
Add an option to initialize automatic variables with either a pattern or with zeroes. The default is still that automatic variables are uninitialized. Also add attributes to request uninitialized on a per-variable basis, mainly to disable initialization of large stack arrays when deemed too expensive. This isn't meant to change the semantics of C and C++. Rather, it's meant to be a last-resort whe
Finding And Fixing Node.js Memory Leaks: A Practical Guide
Fixing memory leaks may not be not the shiniest skill on a CV, but when things go wrong on production, it’s better to be prepared! After reading this article, you’ll be able to monitor, understand, and debug the memory consumption of a Node.js application. When Memory Leaks Become A Problem Memory leaks often go unnoticed. They become a problem when someone pays extra attention to the production p
libFuzzer – a library for coverage-guided fuzz testing. — LLVM 22.0.0git documentation
libFuzzer – a library for coverage-guided fuzz testing.¶ Introduction¶ LibFuzzer is an in-process, coverage-guided, evolutionary fuzzing engine. LibFuzzer is linked with the library under test, and feeds fuzzed inputs to the library via a specific fuzzing entrypoint (aka “target functionâ€); the fuzzer then tracks which areas of the code are reached, and generates mutations on the corpus of input d
ランã‚ング
ランã‚ング
メンテナンス
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Debug UEFI code by single-stepping your Coffee Lake-S hardware CPU
Notes on concurrency bugs
console.log(); ã—ã‹ä½¿ãˆãªã‹ã£ãŸè‡ªåˆ†ã¸ã€‚。。 - Qiita
GitHub - koute/bytehound: A memory profiler for Linux.
https://blogs.oracle.com/linux/post/writing-the-ultimate-locking-check
GitHub - struct/isoalloc: A general purpose memory allocator that implements an isolation security strategy to mitigate memory safety issues while maintaining good performance
GitHub - HallerPatrick/frosch: 🸠Debug faster than a frog catches a fly
Windows guest debugging presentation from KVM Forum 2012
Scudo  | Android Open Source Project
GitHub - cyrus-and/gdb-dashboard: Modular visual interface for GDB in Python
GitHub - google/breakpad: Mirror of Google Breakpad project
DEBIN | Predicting Debug Information in Stripped Binaries
Salzburg '18: Memory-safe and Efficient Execution of C/C++ on the GraalVM
Liz Fong-Jones, Adam Mckaig - Resolving Outages Faster With Better Debugging Strategies
Kdump - ArchWiki
{{#tags}}- {{label}}
{{/tags}}