Explore >> Select a destination
|
You are here 
|
tenthousandmeters.com | ||
| | | | |
tonybaloney.github.io
|
|
| | | | | ||
| | | | |
nikhilism.com
|
|
| | | | | [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. | |
| | | | |
blog.m-ou.se
|
|
| | | | | Have you ever seen the Rust compiler give a Python error? Or better, have you ever seen rust-analyzer complain about Python syntax? In this post, we'll extend our python!{} macro to make that happen. | |
| | | | |
www.lukas-barth.net
|
|
| | | If you build an application that uses large, contiguous amounts of memory, it can increase your performance if you allocate this memory in so-called huge pages. Linux offers you two ways of doing that - a legacy way and a modern way. This article describes the modern way of using huge pages, so called transparent huge pages (THP) and applies the techniques from a previous article to verify that we actually got huge pages. The article starts by giving a super-short recap on how paging works and why huge p... | ||
