sysprof in 2.6.27 kernel
Hello,
is there any port of sysprof gui that cooperates with the current 2.6.27 kernel sysprof tracer?
Signature · 1 line
Lukáš Hejtmánek
Quoted 4 lines · Lukas Hejtmanek
Hello,
is there any port of sysprof gui that cooperates with the current 2.6.27 kernel sysprof tracer?
Yes, the port is accessible from here:
svn checkout http://svn.gnome.org/svn/sysprof/branches/ftrace-branch sysprof
It's somewhat rough still. If you try it out, I will be interested in any feedback you have.
Thanks,
Soren
Quoted 2 lines · Soeren Sandmann
It's somewhat rough still. If you try it out, I will be interested in any feedback you have.
another feedback. I got No map at all processes even at those I got debug info installed.
Signature · 1 line
Lukáš Hejtmánek
Quoted 6 lines · Lukas Hejtmanek
Quoted 2 lines · Soeren Sandmann
It's somewhat rough still. If you try it out, I will be interested in any feedback you have.
another feedback. I got No map at all processes even at those I got debug info installed.
This may be because sysprof user space is not running as root, or it may be because the kernel is generating bogus addresses.
Generally, "No Map" means sysprof is seeing samples in memory regions that are not in /proc/<pid>/maps
Soren
Quoted 6 lines · Soeren Sandmann
Quoted 4 lines · Lukas Hejtmanek
Quoted 2 lines · Soeren Sandmann
It's somewhat rough still. If you try it out, I will be interested in any feedback you have.
Quoted 8 lines
Quoted 2 lines
another feedback. I got No map at all processes even at those I got debug info installed.
This may be because sysprof user space is not running as root, or it may be because the kernel is generating bogus addresses.
Generally, "No Map" means sysprof is seeing samples in memory regions that are not in /proc/<pid>/maps
Actually, I seem to remember one cause of this: the vdso code creates an unusual stackframe where the pointer to the previous frame is stored in an unusual place. I think the sysprof kernel code needs to take this into account, or alternatively send sufficient information to userspace that it can figure it out itself.
Soren
Quoted 2 lines · Soeren Sandmann
This may be because sysprof user space is not running as root, or it may be because the kernel is generating bogus addresses.
if I do not run it as root, the collecor does not start at all.
Quoted 2 lines
Generally, "No Map" means sysprof is seeing samples in memory regions that are not in /proc/<pid>/maps
yes, that could be because only null addresses are received.
Signature · 1 line
Lukáš Hejtmánek
Quoted 2 lines · Soeren Sandmann
It's somewhat rough still. If you try it out, I will be interested in any feedback you have.
and another one. sysproc gui reads user addresses from the sysprof pipe with null pointers. is this ok or is this a bug in sysprof kernel module?
Signature · 1 line
Lukáš Hejtmánek
Quoted 6 lines · Lukas Hejtmanek
Quoted 2 lines · Soeren Sandmann
It's somewhat rough still. If you try it out, I will be interested in any feedback you have.
and another one. sysproc gui reads user addresses from the sysprof pipe with null pointers. is this ok or is this a bug in sysprof kernel module?
That is not ok, but it could happen if the process in question was not compiled with framepointers. Or it could be a bug in the kernel code.
Soren
Quoted 5 lines · Soeren Sandmann
Quoted 2 lines
and another one. sysproc gui reads user addresses from the sysprof pipe with null pointers. is this ok or is this a bug in sysprof kernel module?
That is not ok, but it could happen if the process in question was not compiled with framepointers. Or it could be a bug in the kernel code.
I tried to put printf in case that sysprof gui receives non null address from the kernel. None print was displayed, so it seems ti receives only null addresses.
Signature · 1 line
Lukáš Hejtmánek