This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi - > > Systemtap can pull debugging information out of a vanilla kernel > > that's built/installed from its own Makefile (without rpm), as long as > > CONFIG_DEBUG_INFO was set. > > Do I need special configuration for this to happen? For a vanilla kernel, you should not need more than the CONFIG_DEBUG_INFO option, which you see in the "Kernel hacking" / "Kernel debugging" kernel config screens. The resulting /vmlinux file should be tens of megabytes long. "objdump -h vmlinux" should show a number of large ".debug*" sections. The same applies to kernel module object files. (I assume your platform uses DWARF format debugging information, which is a requirement for systemtap.) > [...] I was not able to figure out how the kernel-debuginfo package > is generated from the kernel source RPM (.spec file). You mean from a Fedora kernel RPM? The debuginfo generation is step is done as an implicit post-processing stage after %build. Unless specifically disabled, it happens automatically when building any rpm from its .src.rpm (rpmbuild). - FChE
Attachment:
pgp00000.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |