![]() ![]() (A core dump is a copy of process memory – the name coming from the era of magnetic core memory – and can be investigated using a debugger.)Ĭore dump analysis is one approach for debugging, but not the only one. Note that it says "Segmentation fault" and not "Segmentation fault (core dumped)". Great! However, when I tested it, it hit a segfault: The bcc collection of BPF tools had a pull request for cachetop, which uses a top-like display to show page cache statistics by process. You also aren't expected to read through all this: I've enumerated each step so you can browse them and find ones of interest. I'll be running the following commands as root, since I'm debugging a tool that needs root access (for now). But it covers the basics and could serve as a tutorial of sorts, bearing in mind there's a lot more to gdb than I used here. This isn't a particularly interesting or exotic issue, it's just a routine gdb debugging session. ![]() It also inspired me to share a full gdb debugging example, with output and every step involved, including dead ends. ![]() I was reminded of the lack of example output when watching the Give me 15 minutes and I'll change your view of GDB talk by Greg Law at CppCon 2015, which, thankfully, includes output! It's well worth the 15 minutes. gdb is the GNU Debugger, the standard debugger on Linux. I'm a little frustrated with finding "gdb examples" online that show the commands but not their output. Systems Performance: Enterprise and the Cloud, 2nd Edition How To Add eBPF Observability To Your ProductīPF binaries: BTF, CO-RE, and the future of BPF perf tools USENIX LISA2021 Computing Performance: On the Horizon USENIX SREcon APAC 2022: Computing Performance: What's on the Horizon ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |