Live data from Hacker News

A flaky test exposed a Redis client use-after-free

buildkite.engineering

11–15 of 15 posts

Re: A flaky test exposed a Redis client use-after-free

#11

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. Wa…

Thanks! This happened two years ago and it took me quite some time to piece together all the information of when it happened. I will see if I can get the original gdb output and add it to the blog post.

Roger that! I'll look forward for an update, and hope to catch the moment and learn from it!

Meanwhile, I do wish you, and the whole team, success, stability, and peace!

Re: A flaky test exposed a Redis client use-after-free

#13
post #12

> Harder still is when the cause of the bug happens prior to its manifestation. I've yet to debug a big where the manifestation happens prior to the cause... Sounds even harder. :p

> I've yet to debug a big where the manifestation happens prior to the cause... Sounds even harder. :p

UB in C++ can have the manifestation occur prior to the cause :-/

Re: A flaky test exposed a Redis client use-after-free

#14

Earlier quoted context omitted.

Thanks! This happened two years ago and it took me quite some time to piece together all the information of when it happened. I will see if I can get the original gdb output and add it to the blog post.

Roger that! I'll look forward for an update, and hope to catch the moment and learn from it! Meanwhile, I do wish you, and the whole team, success, stability, and peace!

Thanks! I’ve added a screenshot of the gdb output to the blog
Post reply on HN