Markus Elfring
Markus Elfring
I constructed a small test program for [the function “QStorageInfo::setPath”](https://code.woboq.org/qt5/qtbase/src/corelib/io/qstorageinfo.cpp.html#155 "Data determination"). I measured execution durations for the used functionality. ``` [Markus_Elfring@fedora QStorageInfo-setPath]$ time sudo uftrace record --data=/home/Markus_Elfring/Test/QStorageInfo-setPath/Probe-uftrace --nest-libcall --kernel...
I tried the following commands out together with the software “uftrace v0.10-76-g3064” once more according to my small test program. ``` [Markus_Elfring@fedora mountedVolumes]$ time sudo uftrace record --data=/home/Markus_Elfring/Test/mountedVolumes/Probe3-uftrace --nest-libcall --kernel-depth=45...
I tried the program „uftrace 0.10-53-gb001“ out together with [the installation program „calamares 3.2.42.20210826-b9f22a75-dirty“](https://github.com/calamares/calamares/ "Distribution-independent installer framework") (for example). I let this software combination run with a trace record command...
I would like to specify that only selected function calls should be traced. [The action „trace_on“ is supported already for triggers](https://github.com/namhyung/uftrace/blob/a663f491e4be2ccf6c0c3f4563226b0ba035d101/doc/uftrace-record.md#triggers "Documentation: uftrace record"). I occasionally see a need to...
A traced program can reach a data processing step after which it can be terminated. How do you think about the possibility to express any conditions for the trace tool...
Would you like to [wrap any pointer data members](https://github.com/fanout/pushpin/blob/9f9b7ff41080701162d68a336da7740f53ca9c59/src/corelib/settings.cpp#L37 "Update candidate") with the template class “[std::unique_ptr](https://en.wikipedia.org/wiki/Smart_pointer#unique_ptr "Description for the usage of smart pointers")”?
:eyes: Some source code analysis tools can help to find opportunities for improving software components. :thought_balloon: I propose to [increase the usage of combined operators](https://www.php.net/manual/en/language.operators.assignment.php#language.operators.assignment.arithmetic "Description for assignment operators") accordingly....
I suggest to add the key word "const" to the type specifiers for parameters like the following. - name (function "[chl_postf](https://github.com/it4e/CHL/blob/8189a9dc0608b7cddb6b5affa11216ad70c9289a/core/src/cgi.h#L20)") - path (function "[file_read_open](https://github.com/it4e/CHL/blob/9aa0e4dd2782b970c8ae4bf619cc7a3de82dd290/core/src/view.h#L14)") Would you like to apply...
I suggest to reuse a higher level build system than [your current small make file](https://github.com/it4e/CHL/blob/d0728ddccdfb6447d37aee7b9df0a371677007d7/makefile#L1) so that powerful checks for software features will become easier. - [CMake](https://cmake.org/) - [Autotools](https://www.gnu.org/software/autoconf/autoconf.html#introduction)
[An extra null pointer check is not needed in functions](https://isocpp.org/wiki/faq/freestore-mgmt#delete-handles-null "Do I need to check for null before delete p?") like the following. - [Graph](https://github.com/PaddlePaddle/Anakin/blob/af7d12fe0a6d2fc25835b8e5080e3b8e22e23a52/framework/graph/graph.h#L49 "Destructor for Graph") - [Node](https://github.com/PaddlePaddle/Anakin/blob/931bf899166c627888d38372f00675b9d85b8d6d/framework/graph/node.h#L124...