Hello,

is there any port of sysprof gui that cooperates with the current 2.6.27 kernel
sysprof tracer?

-- 
Lukáš Hejtmánek
--

[ message continues ]

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
--

[ message continues ]

another feedback. I got No map at all processes even at those I got debug info
installed.

-- 
Lukáš Hejtmánek
--

[ message continues ]

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
--

[ message continues ]

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
--

[ message continues ]

yes, that could be because only null addresses are received.

-- 
Lukáš Hejtmánek
--

[ message continues ]

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?

-- 
Lukáš Hejtmánek
--

[ message continues ]

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
--

[ message continues ]

I tried to put printf in case th