[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 371916] execution tree xtree concept
From:       Philippe Waroquiers <bugzilla_noreply () kde ! org>
Date:       2016-11-05 20:34:32
Message-ID: bug-371916-17878-WX4TilmguM () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=371916

--- Comment #14 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
(In reply to Ivo Raisr from comment #13)
> Thanks for addressing my comments. Especially for providing hints on Xtree
> usage!
> I am happy with the documentation and pub_tool_xtree.h interface.
> However note I have not reviewed any implementation files.
> 
> The last remark I have: have you considered naming the xtree output file
> based on the executed program name, such as <program>.kcg? Currently the
> default xtmemory.kcg will get overwritten every time, even for different
> profiled programs.
For the xtmemory gdbserver command: the user can give a different name if
desired, but the default is to overwrite. This is also the case
for other gdbserver commands producing files, e.g. massif snapshots.

For xtree memory files produced due to command line, the default is similar
to e.g. log files or callgrind output files, or ...:
filename includes %p expanded as pid, to avoid overwriting.
(this %p is needed in particular for forking programs).

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]