sbahra

5 ms·

1.
Squeezing Performance Out of eBPF(bitbison.io)
6 points by sbahra 14d ago|0 comments
2.
Shai-Hulud rebuilt as a standalone stealer(bitbison.io)
3 points by sbahra 1mo ago|0 comments
3.
by sbahra 6y ago
Also up on https://engineering.backtrace.io/2021-01-11-stuff-your-logs/
4.
New Method of Electrical Production That Does Not Require Fossil Fuels(prnewswire.com)
1 points by sbahra 6y ago|3 comments
5.
Umash: A fast and universal enough hash(engineering.backtrace.io)
4 points by sbahra 6y ago|0 comments
6.
Learning from Failures: Better Crash Reporting for Better Incident Response(circonus.com)
3 points by sbahra 6y ago|0 comments
7.
by sbahra 6y ago
Thanks for sharing! For single-writer multi-reader scenario this requires no atomic fences or operations on TSO: http://concurrencykit.org/presentations/lpc2015.pdf Works on any open-addressed scheme (there is also a r
8.
Public virtual event about systems and low-level topics this Thursday(adhoc.community)
1 points by sbahra 6y ago|0 comments
9.
Test case generation for native applications from Python with branch coverage(engineering.backtrace.io)
2 points by sbahra 7y ago|0 comments
10.
Google's Internal TCMalloc is now open-source(github.com)
3 points by sbahra 7y ago|0 comments
11.
by sbahra 7y ago
overthewire.org
12.
by sbahra 7y ago
Give us a spin! Would absolutely love more feedback, it has had a big impact for us already. It’s free for open-source projects. The tool for ASAN/etc... is just a few weeks old but we have been doing crash / error reporting and c
13.
Our Workflows with Address Sanitizer and Valgrind(engineering.backtrace.io)
4 points by sbahra 7y ago|2 comments
14.
Compile Once, Debug Twice: Picking a Compiler for Debbugability(backtrace.io)
2 points by sbahra 7y ago|0 comments
15.
Concurrency Kit: An open-source library for modern concurrent software(concurrencykit.org)
1 points by sbahra 8y ago|0 comments
16.
A Pragmatic Introduction to Multicore Synchronization [Talk](youtube.com)
2 points by sbahra 8y ago|0 comments
17.
The Stale Pointer(backtrace.io)
12 points by sbahra 9y ago|2 comments
18.
Analzying Heap Corruption in the Post-Mortem(backtrace.io)
1 points by sbahra 9y ago|0 comments
19.
Parallel Sections: Scaling System-Level Data-Structures [pdf](pdfs.semanticscholar.org)
2 points by sbahra 9y ago|0 comments
20.
by sbahra 9y ago
Whoops, good catch! I will fix, thanks.
21.
Debug Information Is Huge and What to Do About It(documentation.backtrace.io)
76 points by sbahra 9y ago|20 comments
22.
CPPCon: Optimizations and Debug Quality [pdf](schd.ws)
1 points by sbahra 9y ago|0 comments
23.
by sbahra 9y ago
I'm referring to the FIFO implementation. On the definition of QSBR though, frankly, I think the term gets overloaded in some of the more recent literature in this area. Both EBR and QSBR require that no hazardous references get carrie
24.
by sbahra 9y ago
Great write-up! A few notes worth mentioning (IMO) below: Garbage collection: This is only true in absence of garbage collection. If you're paying garbage collection cost to begin with, this is not an issue. Also, note things such as
25.
by sbahra 9y ago
This is quiescent-state-based reclamation, other implementations exist that are cheap. I have seen the technique you're talking about used in K42 (after I had also thought I invented something novel, when I used the same approach as yo
26.
Comparing the Bias in Telemetry Data vs. The Typical Firefox User(blog.mozilla.org)
1 points by sbahra 9y ago|0 comments
27.
Optimizations and their impact on Debuggers(backtrace.io)
2 points by sbahra 9y ago|0 comments
28.
Compile Once Debug Twice: Picking a Compiler for Debuggability(backtrace.io)
3 points by sbahra 9y ago|0 comments
29.
by sbahra 9y ago
Or use backtrace.io to deal with it. It'll transfer the core dump or a derivative to a centralized server. Transparency: co-founder.
30.
The Debugging Mindset(queue.acm.org)
1 points by sbahra 9y ago|0 comments

More ›