Gregory's Server
 6 comments
@gabrielesvelto Dealt with a bug that would disappear when 'printf' was added or running under debugger! Result of race in code 😞 @mechanicker yeah, it's a good way of widening races or introducing side-effects. In my case a store was being eliminated by the compiler which thought it was dead. Put a printf() right after it and it suddenly works. ~15 years ago I identified a bug in the store-to-load forwarding logic of a prototype CPU by putting a printf() in the right place.  Logging is a valid debugging mechanism though. I used to work on a VoIP library. It needs to run in real time, so if you do pause it on a breakpoint, everything would break after you resume it. Logging was the only practical way to see some state change over time. @grishka yes it is, especially for debugging issues happening only in production environments. For real-time stuff I suggest trying you rr, the ability of moving both backwards and forwards with your debugger means you can record an uninterrupted run and then debug it at will with no timing pressure. |
@gabrielesvelto Are there any plans for x86-64-v3, etc builds for firefox. Or different arm fl builds like https://blog.chromium.org/2023/04/more-ways-were-making-chrome-faster.html