Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Callgrind on Embedded Linux
buha last edited by
I am developing a Qt application running on an embedded target. Debugging with GDB within the Qt creator works on the desktop and on the embedded device.
Now I would like to use Vallgrind or Callgrind. On the desktop this works without problems. All diagrams and calls are displayed. But not on my embedded device. Nothing appears in the different views.
From the output of the console I can take out as far as everything works. I have only the guess that the log file is not transferred to the host PC. On the target the log file "callgrind.out.PID" exists. I can also import the log file manually into the Qt-Creator. Then everything would be displayed correctly. But that should actually go automatically?
Is there any Vallgrind setting in the Qt-Creator, which refers to the file transfer between host and client?
Profiling /tmp/app-qt_graph-prototype stdin: is not a tty stdin: is not a tty ==10170== Callgrind, a call-graph generating cache profiler ==10170== Copyright (C) 2002-2013, and GNU GPL'd, by Josef Weidendorfer et al. ==10170== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==10170== Command: /tmp/app-qt_graph-prototype ==10170== ==10170== For interactive control, run 'callgrind_control -h'. ==10170== ==10170== Events : Ir ==10170== Collected : 1443930 ==10170== ==10170== I refs: 1,443,930 Analyzing finished.
monah_tuk last edited by
Problem too old, but still actual. Is there any way to run callgring on remote embedded linux?