Explore >> Select a destination

You are here

 blog.hakril.net
Understanding Python execution from inside: A Python assembly tracer - Hakril's blog
| | nikhilism.com
Diving into the Python call stack (PyGotham 2018) - Nikhil's blog
3.0 parsecs away

Travel
| | [AI summary] The provided text discusses the process of capturing Python stack traces from a crashed process using Crashpad. It outlines how Python's internal structures, such as frames, code objects, and thread-local storage, are leveraged to extract meaningful crash reports. The text also touches on related work, like sampling profilers, and emphasizes the benefits of reliable crash reporting for productivity and debugging.
| | doughellmann.com
The Performance Impact of Using dict() Instead of {} in CPython 2.7 · Doug Hellmann
4.9 parsecs away

Travel
| |
| | tenthousandmeters.com
Python behind the scenes #4: how Python bytecode is executed
2.0 parsecs away

Travel
| | We started this series with an overview of the CPython VM. We learned that to run a Python program, CPython first compiles it to bytecode, and we...
| | dehora.net
On Rust - Bill de hÓra
20.6 parsecs away

Travel
| Back in 2013, I started a series of posts on programming languages I found interesting. One of the languages I wanted to write about at that time was Rust. As often happens, life got in the way, and it's only now that I'm coming round to a long overdue post. This is one of a series of posts on programming languages and you can read more about thathere.