‹ BackHN Continuity

Thread

Data races and the limits of ThreadSanitizer in C and Go

35 points · 1 comments · matt_d

Loading the complete thread in the background. This saved snapshot is available now. Refresh

  1. 1over137 · · focus · HN ↗
    Nice write up! I didn’t know about those TSan limits; it was informative.
  2. kevinbaiv · · focus · HN ↗

    [dead]

  3. diath · · focus · HN ↗
    Also in my experience once you start reaching out to external libraries instead of sticking to just the standard library of the language, you may run into an issue where TSan starts flagging issues in external libraries and not in your code specifically which took me an embarrassingly long time to figure out you can use suppression env flag to filter out noise from these libraries.
  4. eatonphil · · focus · HN ↗
    Hey HN! While I've got you, I also just made all internships we've indexed publicly available and searchable without an account needed. Happy job hunting!

    <a href="https:&#x2F;&#x2F;theconsensus.dev&#x2F;internships.html" rel="nofollow">https:&#x2F;&#x2F;theconsensus.dev&#x2F;internships.html

  5. codedump · · focus · HN ↗

    [dead]

  6. camkego · · focus · HN ↗
    I’ve often thought that single threaded architectures that can eliminate whole classes of bugs are often undervalued.

    For example, the command execution design of Redis is purely single threaded. (Redis does have other threads for slower activities)

    1. pjmlp · · focus · HN ↗
      Because we were already there with multi-processing and OS IPC before mainstream OSes added multi-threading support, and while it is better for stability and security, there are additional hardware resources to account for.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.