There seem to be two separate issues:

1) The first issue seems to be about deployment.

I am building on "d:\sources\Qt\GammaRay-2.0.1\build\", and deploying to 
"c:\Program Files (x86)\GammaRay\"
I can start gammaray without options, and the launcher does show when running 
from "d:\sources\Qt\GammaRay-2.0.1\build\bin\"
However, the launcher will not show when running from "c:\Program Files 
(x86)\GammaRay\bin\"

This one is easy enough for me to circumvent.

Files in my target bin folder (drive C):
gammaray_common-qt4.8-MSVC-debug-i686.dll
gammaray_core-qt4.8-MSVC-debug-i686.dll
gammaray_ui-qt4.8-MSVC-debug-i686.dll
gammaray.exe
gammaray-client.exe
gammaray-launcher.exe

Note: I have run nmake install with Admin rights.

2) GammaRay will still not attach to my process
With In-Process, nothing happens at all.
With Out-Of-Process, an empty command line window appears, but nothing else 
happens.
I have tried running my application both with and without debugger attached.


Kind regards

Robert Schimkowitsch 
Automation
Development Control Center Systems 
ANDRITZ HYDRO GmbH
Eibesbrunnergasse 20
1120 Vienna, Austria
Phone: +43 50805 56767
e-mail: robert.schimkowit...@andritz.com 
Internet: www.andritz-hydro.com


-----Original Message-----
From: Volker Krause [mailto:volker.kra...@kdab.com] 
Sent: Donnerstag, 27. März 2014 16:45
To: gammaray-inter...@kdab.com
Cc: Schimkowitsch Robert
Subject: Re: [Gammaray-interest] Since 2.0, GammaRay doen't work at all

On Tuesday 25 March 2014 07:14:13 Schimkowitsch Robert wrote:
> I don't know where to report this, but since Version 2.0, GammaRay has
> stopped working completely. I have tried both 2.0 and 2.0.1
> 
> Contrary to the command line output, starting GammaRay without command line
> parameters does nothing except show the help output. Starting
> GammarayLauncher, you can select a process to attach to. The most that
> happens is that an empty command line window opens, nothing more. Same
> thing when you attach to a process via the command line. I've tried all
> three attaching options (in-process, out-of-process with local or remote
> debugging). With out-of-process, I get the empty command line, with
> in-process I get nothing at all.

This sounds like it's not finding the helper executables (gammaray-
launcher.exe, gammaray-client.exe). I assume you are calling gammaray.exe in 
the bin folder of the build directory? The other executables should be right 
next to it. If they are, could you post the content of config-gammaray.h (one 
level above "bin"), especially the GAMMARAY_INVERSE_xxx_DIR #defines. If they 
got messed up, it would explain this behavior.

regards,
Volker

> Configuration:
> Windows 7x64
> VS 2010 SP 1
> Qt 4.8.1
> cmake 2.8.12.2
> No additional GammaRay plugins, just what the branch zipfile from Git
> contains.
> 
> I've built GammaRay with exactly that configuration, and I am using it on
> applications built with the very same configuration.
> 
> GammaRay 1.3 is working....sort of.
> 
> Kind regards
> 
> Robert Schimkowitsch
> ________________________________
> 
> This message and any attachments are solely for the use of the intended
> recipients. They may contain privileged and/or confidential information or
> other information protected from disclosure. If you are not an intended
> recipient, you are hereby notified that you received this email in error
> and that any review, dissemination, distribution or copying of this email
> and any attachment is strictly prohibited. If you have received this email
> in error, please contact the sender and delete the message and any
> attachment from your system.
> 
> Thank You.
> 
> ________________________________

-- 
Volker Krause | volker.kra...@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-independent software solutions
_______________________________________________
Gammaray-interest mailing list
Gammaray-interest@mail.kdab.com
https://mail.kdab.com/mailman/listinfo/gammaray-interest

Reply via email to