6 comments

  • serious_angel 24 minutes ago

    Thank you very much! This is great read! Though, no actual steps mentioned, including the:

    > From this, he ascertained that the exception was triggered by a call to the C function memmove. While the source and destination addresses for this call looked sane, the size field was set to...

    I do get the most of these stated, but it would be awesome to know more about how he did actually find it, and with what toolset. Was is gdb, Valgrind, JetBrains, IDA Pro, or some another general/complex dump viewer/toolset?

    And, the interactive miracle, at the top of the website is freaking marvelous... It reminded me of the articles of the fluid simulation algorithms of Yusuke Endoh! Heartfelt gratitude to the developer, the artist who implemented it!

  • VerifiedReports 33 minutes ago

    That makes no grammatical sense.

      Retr0id 31 minutes ago

      Works on my machine. (Even though HN's filters removed the leading "How")

        VerifiedReports 27 minutes ago

        I don't think you're replying to the right comment, since I didn't mention anything working.

          Retr0id 26 minutes ago

          The "machine" in question is my brain (or at least, the part of it that parses grammar).

      paulannesley 27 minutes ago

      A (flaky test) exposed a (Redis client) use-after-free [bug]