Marcus, Are you referring to the debug kernel for i386? I was referring to x86_64. I checked kernel-source-2.6.16.16-2.x86_64.rpm. The .config file for x86_64/debug does not have either CONFIG_DEBUG_INFO or CONFIG_FRAME_POINTER set. I propose that both these options be set for the debug kernel. CONFIG_DEBUG_INFO should be set for the default kernel. Without this, backtracing will not work for user space applications with oprofile. Fedora Core has this option set with their latest kernel release. Thanks Kay Tiong On May 25, 2006, at 6:40 PM, Marcus Meissner wrote:

On Thu, May 25, 2006 at 04:02:52PM +0800, Kay Tiong Khoo wrote:

...

Hello there,

I have several questions with regard to oprofile backtracing support in the kernel and would appreciate responses from SUSE Developers.

1. Currently, CONFIG_DEBUG_INFO is not set on openSUSE and SLES9. Will it be set in future SUSE products? This is required for oprofile backtracing to work in user space.

2. Because CONFIG_FRAME_POINTER is not set on openSUSE and SLES9, samples in the kernel will not have backtraces. Is there any possibility that future releases of openSUSE and SLES will have CONFIG_FRAME_POINTER set?

I am currently in the process of developing a front-end with a rewritten oprofile kernel module as the backend. Proper support for backtracing on SUSE products will help customers properly visualize the callstacks.

Check out the kernel-debug kernel. It has above features.

Ciao, Marcus

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org