18:06 <azonenberg> i just spent a whole day hunting down this bug... writing to a FIFO with data synchronous to clock A

18:06 <azonenberg> when you told the buffer to sample on clock B, which has no phase relationship

18:06 <azonenberg> tends to not end well

18:06 <azonenberg> silly typos :P

18:09 <larsc> that's why I want tools which are clock domain aware

18:10 <azonenberg> larsc: yeah, that would be nice

18:11 <azonenberg> This is a textbook mandelbug lol

18:11 <azonenberg> "A bug whose underlying causes are so complex and obscure as to make its behavior appear chaotic or even non-deterministic. This term implies that the speaker thinks it is a Bohr bug, rather than a heisenbug"

18:13 <wpwrak> as long as you don't up with schroedingerbugs ..

18:14 <larsc> azonenberg: yea, it's a nice method for introducing random failures

18:17 <azonenberg> wpwrak: "A design or implementation bug in a program that doesn't manifest until someone reading source or using the program in an unusual way notices that it never should have worked, at which point the program promptly stops working for everybody until fixed" - lol

18:17 <azonenberg> i know those

18:26 <wpwrak> and of course, there are the everett bugs. but they're pretty common. (after Hugh Everett, discoverer of the many-worlds interpretation)

18:29 <azonenberg> lol