[Gammaray-interest] Gui missing half of the tools

[Volker Krause]

On Tuesday, 7 May 2019 06:14:38 CEST Christian Gagneraud wrote:
> On Tue, 7 May 2019 at 02:49, Volker Krause <volker.krause at kdab.com> wrote:
> > Hi,
> > 
> > that sounds like missing (or incompatible) tool plugins, either on the
> > target side (and thus really only the built-in tools existing), or on the
> > host side so that the tools exist on target but there is just no UI for
> > them.
> > 
> > Other reasons like issues with the build configuration as you mentioned
> > could cause this too, but I'd start by checking the tool plugins on both
> > the target and the host.
> 
> The target looks OK:
> root at NSS3-0a-b6-d9:~# find /usr/lib/gammaray/ -name '*.so' | sort
> /usr/lib/gammaray/2.10/qt5_12-arm/gammaray_3dinspector.so
[...]

yep, that looks correct. Possible things to verify there:
- check with qtplugininfo that the plugins have the right Qt version baked in, 
otherwise the Qt plugin loader will reject them
- check with ldd (does that exist on QNX?) if the plugins find their 
dependencies
- run the target with QT_DEBUG_PLUGINS=1 set, that should show if the Qt 
plugin loader is finding the plugins and if so, if they fail to load for some 
reason.

> The host as well:
> chgans at chgans-workstation:~/Projects/GammaRay$ find
> build/lib/gammaray/ -name '*.so' | sort
> build/lib/gammaray/2.11/qt5_9-x86_64/gammaray_3dinspector.so
> build/lib/gammaray/2.11/qt5_9-x86_64/gammaray_3dinspector_ui.so
[...]

This also looks correct. The mixing of GammaRay versions isn't well tested, 
it's always possible we missed a subtle protocol change, but that would 
usually result in other kinds of misbehavior.

Besides the general Qt plugin loading checks mentioned for the target, an 
additional check is to run the client with GAMMARAY_DEVELOPERMODE=1, that 
gives you an additional 'Diagnostics' sub-menu in the 'Help' menu. The entry 
'Plugins' there should show  a list of plugins the target sees (ie. this 
should not be empty), and the "Message Statistics" view shows on the left all 
GammaRay objects present in the server, if you see anything there beyond 
QtCore (e.g. widget or qtquick related things), that would indicate the 
plugins are actually loaded.

> './bin/gammaray --connect tcp://mfd:1234' only shows:
>  - Messages
>  - Meta Objects
>  - Meta Types
>  - Objects
>  - Problems
>  - Resources

That is exactly the list of built-in tools, which suggests there's indeed a 
problem with the plugins.

Regards,
Volker

> Other devs had the same problem with gammaray-2.10 on Linux and Windows.
> 
> Chris
> 
> > Regards,
> > Volker
> > 
> > On Saturday, 4 May 2019 01:13:10 CEST Christian Gagneraud wrote:
> > > Hi there,
> > > 
> > > Probe is arm-linux 2.10
> > > GUI is x86_64 Linux and Windows (master or 2.10).
> > > When the GUI connects to the remote device, it's missing half (at
> > > least) of the tools.
> > > Only QObject related tools are available (and a couple of others).
> > > 
> > > I haven't investigated yet, Could that come from gammaray probe build
> > > time? Is there any known issues?
> > > 
> > > AFAIR, it use to work correctly, the only thing i can think of is that
> > > we've recently switched our embedded platforms from Qt-5.6 to Qt-5.12.
> > > 
> > > Thanks,
> > > Chris
> > > _______________________________________________
> > > Gammaray-interest mailing list
> > > Gammaray-interest at mail.kdab.com
> > > https://mail.kdab.com/mailman/listinfo/gammaray-interest
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4664 bytes
Desc: not available
URL: <http://mail.kdab.com/pipermail/gammaray-interest/attachments/20190507/61d315f3/attachment-0001.p7s>