How to profile PySide2 + QML in QtCreator? - qt

I have a PySide2 application, which uses QML to display the user interface. The application works from the command line. I can also launch it as well as debug it in QtCreator. However, when I try to run QmlProfiler, I see the following error:
:-1: error: /home/username/code/project/venv/bin/python: Error while finding module specification for 'ljsdebugger=file:/tmp/QtCreator-kVUFuF/qtcreator-freesocket.XgLEKq,block,services:CanvasFrameRate,EngineControl,DebugMessages,DebugTranslation' (ModuleNotFoundError: No module named 'ljsdebugger=file:/tmp/QtCreator-kVUFuF/qtcreator-freesocket')
I checked project's kit settings and it is using all the defaults. I could not find any relevant articles/discussions with this error message on the web. How to resolve this issue?

Solving this involves two steps:
Make the application debugging enabled
Add the line before QApplication is instantated:
from PySide2.QtQml import QQmlDebuggingEnabler
debug = QQmlDebuggingEnabler()
Connect it to the QML Profiler
run the application with the command line parameter: -qmljsdebugger=port:10002,block with the port of your choice. Then go to Analyze>QML Profiler (Attach to Waiting Application) and choose the port you started the program with:
This successfully connected the program to the QML Profiler.

from PySide6.QtQml import QQmlDebuggingEnabler
debug = QQmlDebuggingEnabler()
it also useful in pyside6 , tks bro #WhiteStork

Related

No main manifest attribute, Netbeans

I have the following problem when trying to launch a .jar file of my program in cmd: no main manifest attribute, in path/filename.jar
I tried to add the Main-Class to the MANIFEST.MF file, but then it says Error: Could not find or load main class.
In NetBeans I have set the Main Class at Properties->Run->Main Class to the one, which holds the function main(String[] args) in my case "com.nxp.vda_with_gui_1.version.App". I have also added VM Options for the JavaFX modules like the following:
--module-path C:\NetbeansJavaFX --add-modules javafx.controls,javafx.base,javafx.fxml,javafx.graphics,javafx.media
In NetBeans I can build and launch up my program without any errors, but when I try to "Run File" (Shift + F6) a different error will be put out:
Error: JavaFX runtime components are missing, and are required to run this application Command execution failed.
Any tips how to solve it?
Below you can find a picture of my file/package structure and some other information, maybe it helps finding a solution quicker:
file/package structure
JDK version: 16
JavaFX version: 18.0.2
OS: Windows

Errors while compiling the generated C++ SDK

I have installed the kaa server and did a compilation of a SDK i generated, first everything went well but after i changed the IP settings in the administrative GUI of the kaa-server things went wrong.
The C++ SDK wont compile anymore and gives the following error:
In file included from kaa/IKaaClientStateStorage.hpp:24:0,
from kaa/channel/transport/IKaaTransport.hpp:20,
from kaa/channel/transport/AbstractKaaTransport.hpp:20,
from kaa/event/registration/UserTransport.hpp:22,
from /impl/event/registration/UserTransport.cpp:17:
kaa/notification/gen/NotificationDefinitions.hpp:34:27: error: ‘Notification’ in namespace ‘kaa_notification’ does not name a type
typedef kaa_notification::Notification KaaNotification;

Release does not run. This application failed to start

My application works when it built in debug mode. But it does not run in release.
This application failed to start because it could not find or load the
Qt platform plugin "windows".
Reinstalling the application may fix this problem.
I copied dlls which the application required. I copied also qwindows.dll, qoffscreen.dll and libEGL.dll.
But libEGL.dll located in C:\qt\5.3\msvc2013\bin and `C:Qt\ToolsQtCreator\bin'. I compiled my application by msvc-11.0(2012).
--
I put platforms folder to exe directory and now application runs but crashes immediately in ntdll.dll!771e56bc()
Now my problem is similar to this one Why is ntdll.dll crashing my c++ executable?.
Can I make debug working like release but save debug mode?
--
Here is Application Verifier result for release mode. It does not happen for debug.
=======================================
VERIFIER STOP 00000006: pid 0xDF0: Corrupted heap pointer or using wrong heap.
00161000 : Heap handle used in the call.
093F8FF8 : Heap block involved in the operation.
00000004 : Size of the heap block.
06441000 : Heap where block was originally allocated.
=======================================
This verifier stop is not continuable. Process will be terminated
when you use the `go' debugger command.
=======================================
MyApp.exe has triggered a breakpoint.
AVRF: Noncontinuable verifier stop 00000006 encountered. Terminating process ...
The thread 0x1724 has exited with code -1073740767 (0xc0000421).
The program '[3568] MyApp.exe' has exited with code -1073740767 (0xc0000421).
--
Here is a top of a call stack
vrfcore.dll!6ae43466() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for vrfcore.dll]
[External Code]
qwindows.dll!0f0642cb() Unknown
qwindows.dll!0f065f8a() Unknown
qwindows.dll!0f0662bb() Unknown
Qt5Gui.dll!0f774cf3() Unknown
Qt5Gui.dll!0f774e75() Unknown
Qt5Gui.dll!0f7778d5() Unknown
But libEGL.dll located in C:\qt\5.3\msvc2013\bin and `C:Qt\ToolsQtCreator\bin'
You must not take any DLLs from C:\Qt\Tools\QtCreator\ -- these are private DLLs for Qt Creator, and they are incompatible with your application.
Only take DLLs from C:\Qt\5.3\msvc2013\bin and C:\Qt\5.3\msvc2013\plugins. Here is the required folder structure:
(source: http://qt-project.org/wiki/Deploy_an_Application_on_Windows )
This sounds like either a DLL is missing or the application expects it in a different path.
a) Use the Dependency Walker on your release build executable to check whether all DLL dependencies can be resolved.
b) Make sure that your platform plugin files are at the right location. I think they need to be in a folder called "platforms" (not absolutely sure though).
c) There is a post in the Qt forum about a similar problem. Maybe this helps you to track it down.

New Static Library has build error "libtool exited with code 1"

I created a new static library in my iOS project and now I'm getting the build error
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/libtool failed with exit code 1
How do I go about debugging this?
To see the actual output and not just the error message, try building your target or scheme with xcodebuild from command line.
I had a problem with the same error message. In my case, I couldn't build for the simulator, but it worked find when building for the device. The output from xcodebuild confirmed that Xcode could not set the proper architecture to build for the simulator.
Long story short, it turned out that one build setting was corrupted. The Mach-O Type setting in the Linking category was set to Relocatable Object File for some reason. I switched it back to Static Library and the error disappeared.

Depmod - unresolved symbols in rt73 module

I'm trying to install a linux driver for my wireless network card (D-Link DWL-G510) on my Red Hat Linux 7.1 machine with a 2.4.37.9 kernel. I downloaded the serial monkey driver from the sourceforge site and was able to successfully compile the module. However, whenever I do a "make install", the make script executes a "depmod -a" command which then complains with the message: "Unresolved symbols in /lib/modules/2.4.37.9/extra/rt73.o".
I then executed a "depmod -e" command to show unresolved symbols and it indicates the following information:
request_firmware_Rsmp_38ce5074
release_firmware_Rsmp_33934162
I did a grep on the above information and it showed no source files making reference to it. I searched for it on google and it returned no results. Can anyone help?
I found out the reason - it was missing the firmware_class module. I had to rebuild kernel modules with the experimental feature CONFIG_FW_LOADER as a module which is found under Library routines\Hotplug firmware loading support. After loading the firmware_class module, the rt73 module loaded successfully also.

Resources