« earlier | later » Page 1 of 4
iosnoop For Linux edit / delete
"How does this work? It's just a shell script!" Linux's ftrace facility turns out to be surprisingly capable... and there are a whole load of neat scripts that use it in perf-tools.
to debugging ftrace linux perf performance tracing ... on 14 October 2016
Notes on concurrency bugs edit / delete
A couple of studies (now a few years old) looking at what kinds of concurrency bugs show up in real software.
to concurrency correctness debugging software-engineering ... on 28 August 2016
GP-01 by Genesis Project :: pouët.net edit / delete
The CGA demo that needed fixes to work on a real CGA card...
Embedded in Academia : Multi-Version Execution Defeats a Compiler-Bug-Based Backdoor edit / delete
Using varan, a tool that compares execution traces of programs built in different ways, to detect a compiler fault. Neat!
to compiler debugging security varan ... on 28 February 2016
rr: lightweight recording & deterministic debugging edit / delete
Sounds like a neat idea. Unfortunately it requires 32-bit compilation, so it's not going to work on GARStow.
A zine about strace - Julia Evans edit / delete
"As some of you might have heard, I wrote a zine to teach people about how to debug their programs using strace a while ago!" One of my favourite tools too.
"Collection of tools to remotely debug PS2 applications, including commercial PS2 games". Used by the current PS2 Linux port.
to debugging homebrew playstation ps2 software ... on 18 January 2015
"For every resource, check utilization, saturation, and errors."
to ag0803 analysis benchmarking debugging networking performance ... on 24 August 2014
The Last Line Effect edit / delete
An interesting observation on copy-paste errors.
to copy-paste debugging errors programming ... on 26 July 2014
Memory usage tracking for GDB. "gdb-heap is different in that it allows for unplanned memory usage debugging: if a process unexpectedly starts using large amounts of memory you can attach to it with gdb, and use a new heap command to figure out where the memory is going."
to debugging gdb heap memory performance ... on 28 April 2014
« earlier | later » Page 1 of 4
- debugging | |
5 | + ag0700 |
1 | + ag0801 |
2 | + ag0803 |
1 | + algorithm |
1 | + analysis |
1 | + assembler |
1 | + benchmarking |
1 | + bug |
2 | + bugs |
1 | + build |
1 | + cga |
1 | + clang |
1 | + compiler |
2 | + concurrency |
1 | + copy-paste |
1 | + correctness |
1 | + demo |
1 | + errors |
1 | + ftrace |
3 | + games |
1 | + gcc |
2 | + gdb |
1 | + haskell |
1 | + heap |
1 | + homebrew |
1 | + kernel |
1 | + ld |
1 | + libc |
7 | + linux |
1 | + llvm |
1 | + lockfree |
1 | + memory |
1 | + networking |
1 | + opengl |
1 | + pacman |
1 | + pc |
1 | + perf |
4 | + performance |
1 | + playstation |
1 | + pokemon |
1 | + profiling |
3 | + programming |
1 | + ps2 |
2 | + python |
3 | + research |
1 | + scalzi |
1 | + scheme |
1 | + security |
14 | + software |
1 | + software-engineering |
2 | + strace |
2 | + stuffed-animal |
1 | + systemtap |
2 | + teaching |
1 | + to-package |
3 | + tracing |
1 | + valve |
1 | + varan |
1 | + windows |
tasty by Adam Sampson.