On 03.12.2024 13:42, Randy Dunlap wrote:
On 12/2/24 1:41 AM, Sebastian Fricke wrote:
Hey Randy,
On 30.11.2024 00:10, Randy Dunlap wrote:
Hi,
It seems to me that documentation for kgdb should be in the new /debugging/
sub-directory [or that all of /debugging/ should be under dev-tools].
Same treatment for gdb-kernel-debugging.rst.
Any comments about those?
Thanks I have overlooked these files, but yes I would say these are good
candidates for the new debugging directory. And then we can link those
pages into the userspace debugging advice guide.
I'm working on this move unless you want to do it.
Yes please go ahead :).
I don't think that we quite agree on adding links to kgdb & gdb into the
userspace debugging advice guide. I would prefer to see them in the
driver development debugging guide or only listed in debugging/index.rst.
Well within the driver development debugging guide I have written the
following in the introduction:
```
While this guide focuses on debugging that requires re-compiling the
module/kernel, the :doc:`userspace debugging guide
</process/debugging/userspace_debugging_guide>` will guide
you through tools like dynamic debug, ftrace and other tools useful for
debugging issues and behavior.
```
I would say your right about KGDB as that requires you to recompile with
something like:
```
# CONFIG_STRICT_KERNEL_RWX is not set
CONFIG_FRAME_POINTER=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
```
But for GDB you only need to activate debug info, which is not just
useful for GDB and it is a debugging method that you do from userspace
with a userspace tool, which to me sounds very fitting for the userspace
debugging guide.
But I am happy to hear your arguments if you feel like I misjudge this.
thanks.
--
~Randy
Regards,
Sebastian Fricke
