Lines Matching full:we

34 we're not stuck debugging undefined behaviour should it turn out that you were
52 elide - if we were working in a language with embedded correctness proofs that
54 still be a few decades before it comes to systems programming languages. But we
64 introspection. We can't debug anything if we can't see what's going on.
66 Whenever we're debugging, and the solution isn't immediately obvious, if the
67 issue is that we don't know where the issue is because we can't see what's
70 We have the tools to make anything visible at runtime, efficiently - RCU and
83 labels, and good structure - we don't want files with a list of bare integers,
91 tool, but always look for more immediate ways to make things visible. When we
92 have to rely on tracing, we have to know which tracepoints we're looking for,
93 and then we have to run the troublesome workload, and then we have to sift
172 tools we use for testing. The shortest possible edit/test/debug cycle is
173 essential for working productively. We learn, gain experience, and discover the