Backtrace Blog
backtrace.io · Company blog · on HN since 2014
The company blog of Backtrace, a crash and error debugging vendor, with technical posts on core dumps, memory bugs, and concurrency.
What HN saysCommenters praise posts like the one on picking a compiler for debuggability, and the company often uses HN to post job openings.
16HN people shared it
5linked it in comments
33stories submitted
528story points
6 years agolast shared
2014people per year2026
Most-shared posts
- 1Fast Bounded-Concurrency Hash Tables3 people · 83 points · first shared 2015 · 4 comments on HN
- 2The Stale Pointer3 people · 26 points · first shared 2018 · 2 comments on HN
- 3Compile Once Debug Twice: Picking a Compiler for Debuggability3 people · 6 points · first shared 2017 · discussion on HN
- 4Homepage3 people · first shared 2015
- 5What is a core dump and how do you parse one?2 people · 121 points · first shared 2015 · 19 comments on HN
- 6Post-Mortem Heap Analysis: TCMalloc2 people · 9 points · first shared 2016 · discussion on HN
- 7Post-Mortem Memory Debugging2 people · 6 points · first shared 2016 · discussion on HN
- 8Memory Management Bugs: An Introduction2 people · 6 points · first shared 2016 · discussion on HN
- 9Compile Once, Debug Twice: Picking a Compiler for Debbugability2 people · 2 points · first shared 2019 · discussion on HN
- 10Performance Improvements for FreeBSD Kernel Debugging1 people · 61 points · first shared 2016 · 2 comments on HN
- 11ELF Shared Library Injection Forensics1 people · 46 points · first shared 2016 · 2 comments on HN
- 12Exploiting ELF Expansion Variables1 people · 46 points · first shared 2016 · 4 comments on HN
- 13Faster Backtraces for Native Applications1 people · 46 points · first shared 2014 · 10 comments on HN
- 14Implementing a Debugger: The Fundamentals1 people · 33 points · first shared 2016 · 5 comments on HN
- 15Fast Bounded-Concurrency Hash Tables1 people · 10 points · first shared 2017 · discussion on HN
What HN people wrote when they linked it
rashkov · 2021-04-12
Backtrace (https://backtrace.io) | Full Stack Engineer (frontend, backend) | REMOTE or New York City
Backtrace.io is hiring for a full stack engineer. Ideal candidate should have a strong knowledge of React and Javascript, as well as interest in or experience with ReasonML / ReScript.
If you’re interested in applying or have any general questions, please get in touch with me at [email protected]
FULL-STACK ENGINEER (FRONTEND FOCUS)
Backtrace is dedicated to building the best debugging technology for today’s software. Our flagship product improves software reliability, quality, and support by automating software error detection, response, and resolution. Backtrace is used by everything from the most popular video games, consumer electronics, productivity tools to large-scale appliances and server infrastructure. We’re a diverse, technical group joined by a mission to make software better, and are looking to add a full-stack engineer with a frontend/UI focus to complement our dynamic user-interface.
The position is remote and our engineering team is distributed across the globe.
2-3+ years of frontend engineering experience.
1-3+ years of Node API design and implementation.
Fluency using Javascript, HTML/CSS, ReactJS (or an equivalent modern frontend framework), git.
Experience with Single Page Application architecture
You have initiative and are able to see it through when given the opportunity.
You are passionate and care about building a culture of learning and…
loeg · 2017-10-31
Minor typo:
> A more efficient representation of .debug_rnglists introduced in DWARF 5.
Should probably read:
> A more efficient representation of .debug_ranges introduced in DWARF 5.
Edit: Tangentially, I loved https://backtrace.io/blog/compile-once-debug-twice-picking-a-compiler-… and am still looking forward to parts 2 and 3. Thanks!
sbahra · 2015-11-25
Yes, it is possible. We are hiring, learn more at http://Backtrace.io
fsaintjacques · 2019-08-26
See https://backtrace.io, disclaimer, previous employee.
pasbesoin · 2016-08-26
URL to prior blog entry is borked. Adding a trailing forward slash fixes:
http://backtrace.io/blog/blog/2015/10/03/whats-a-coredump/