On Mon, Apr 12, 2021 at 3:43 AM Marco Elver wrote:
>
> On Sat, 10 Apr 2021 at 13:53, Daniel Latypov wrote:
> > On Sat, Apr 10, 2021 at 12:05 AM David Gow wrote:
> [...]
> > > +
> > > +
> > > +Sanitizers
> > > +==
> > > +
>
> The "sanitizers" have originally been a group of tools that
On Sat, Apr 10, 2021 at 12:05 AM David Gow wrote:
>
> The kernel now has a number of testing and debugging tools, and we've
> seen a bit of confusion about what the differences between them are.
>
> Add a basic documentation outlining the testing tools, when to use each,
> and how they interact.
On Sat, 10 Apr 2021 at 13:53, Daniel Latypov wrote:
> On Sat, Apr 10, 2021 at 12:05 AM David Gow wrote:
[...]
> > +
> > +
> > +Sanitizers
> > +==
> > +
The "sanitizers" have originally been a group of tools that relied on
compiler instrumentation to perform various dynamic analysis
A nit but
> +The bulk of kernel tests are written using either the :doc:`kselftest
> +` or :doc:`KUnit ` frameworks. These both provide
> +infrastructure to help make running tests and groups of tests easier, as well
> +as providing helpers to aid in writing new tests.
If you just mention the
On Sat, Apr 10, 2021 at 12:05 AM David Gow wrote:
>
> The kernel now has a number of testing and debugging tools, and we've
> seen a bit of confusion about what the differences between them are.
>
> Add a basic documentation outlining the testing tools, when to use each,
> and how they interact.
The kernel now has a number of testing and debugging tools, and we've
seen a bit of confusion about what the differences between them are.
Add a basic documentation outlining the testing tools, when to use each,
and how they interact.
This is a pretty quick overview rather than the idealised
6 matches
Mail list logo
