Hi,
I am running valgrind 3.4.1 on a ppc32 system, using uClibc. I am using
3.4.1 because 3.5.0 won't compile for ppc32.
I am running a multi-threaded program under callgrind, viewing the call
graph in kcachegrind.
The output looks reasonably sane, up to a point. But if I turn off cycle
detection in kcachegrind, I see some function calls which just don't make
sense (e.g. fprintf calling one of my application's functions).
If I turn cycle detection on, almost all of the cycles seem to get folded
up into a nameless call labelled as "<cycle 2>" in libpthread.so
This leads me to believe that the call graph is getting befuddled by
pthread context switches. Is this a fair assumption? Is it a known
problem? Is there anything I can do about it?
Thanks very much,
Stuart
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
