Lines Matching +full:full +full:- +full:custom

1 .. SPDX-License-Identifier: GPL-2.0
9 While this guide focuses on debugging that requires re-compiling the
23 ------------------
38 - No need to learn anything, simple to use
39 - Easy to modify exactly to your needs (formatting of the data (See:
40   :doc:`/core-api/printk-formats`), visibility in the log)
41 - Can cause delays in the execution of the code (beneficial to confirm whether
46 - Requires rebuilding the kernel/module
47 - Can cause delays in the execution of the code (which can cause issues to be
50 For the full documentation see :doc:`/core-api/printk-basics`
65 For the full Documentation see trace_printk()
79 <process/coding-style:13) printing kernel messages>`. In almost all cases the
83 Custom printk
99 <https://lore.kernel.org/all/2024032757-surcharge-grime-d3dd@gregkh>`_.
102 ------
104 Creating a custom Ftrace tracepoint
115 For the full event tracing documentation see :doc:`/trace/events`
117 For the full Ftrace documentation see :doc:`/trace/ftrace`
120 -------
131 Possible use-cases among others:
133 - Store register values
134 - Keep track of variables
135 - Store errors
136 - Store settings
137 - Toggle a setting like debug on/off
138 - Error injection
147 - Create a directory during probe (``struct dentry *parent =
149 - Create a file (``debugfs_create_u32("my_value", 444, parent, &my_variable);``)
151   - In this example the file is found in
154   - any read of the file will return the current contents of the variable
157 - Clean up the directory when removing the device
160 For the full documentation see :doc:`/filesystems/debugfs`.
163 ----------------------------------------------
170 KASAN is a dynamic memory error detector that helps to find use-after-free and
171 out-of-bounds bugs. It uses compile-time instrumentation to check every memory
174 For the full documentation see :doc:`/dev-tools/kasan`.
185 For the full documentation see :doc:`/dev-tools/ubsan`
193 and other locking-related issues in the kernel.
208 ---------------
215 rules to copy that file somewhere for long-term storage and analysis, as by
217 5 minutes. That data is analyzed with driver-specific tools or GDB.
231 .. kernel-doc:: include/linux/devcoredump.h
233 .. kernel-doc:: drivers/base/devcoredump.c