Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Thank you, Maarten,

I've run office like so from within the Python script:

  p = subprocess.Popen("valgrind --tool=callgrind soffice 
--accept=\"socket,host=localhost,port=2002;urp;StarOffice.ServiceManager\"", shell=True, env=myenv)

and got five callgrind.out.* files once the script terminated soffice.
I ran those through

  callgrind_annotate callgrind.out.*

Note that I'm using the default office image which (I assume) has no
debug symbols.  The data doesn't make much sense.  Considering the loop
in question ran for about ~45sec (with and without valgrind?!) then I'd
expect an instruction count _much_ larger than a few hundreds of
thousands.  In all four profiles, though, libc's _dl_addr and ld's symbol
lookup take most of the time.  Not sure I trust these profiles.

Attached.

Jens


On Wed, Dec 31, 2014 at 09:09:19AM +0100, Maarten Hoes wrote:
   Hrm.
   Perhaps a wiki page may not be needed after all; it doesnt seem to get
   more complicated than this ? :
   valgrind --tool=callgrind instdir/program/soffice
   And then load the contents of callgrind.out.<pid> in KCachegrind ?
   - Maarten

-- 
Jens Tröger
http://savage.light-speed.de/

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.