QAxObject SIGSEGV

Maxbester

Still no reply and still no solution.

I realised the problem occurs when I try to access a method when the ActiveX connection is not established yet.

SGaist

Hi,

I'm not a QAx specialist, but are you sure your object is valid when you try to call that method ?

Maxbester

Absolutely not. That's the point. The object is sometimes valid but not always and I don't know how to check it...

SGaist

Can you show how you create it and use it ?

Maxbester

I use a tlb file. My .pro file has:

@TYPELIBS = $$system( dumpcpp lib/Pulse.tlb -n PulseLabShop -o src/controller/Pulse )@

Then I create the connection with:

@PulseLabShop::Application *app = new PulseLabShop::Application();@

In a destructor I have:

@
app->CloseProject(true);
app->Quit();
@

But if the connection has been lost I have a SIGSEGV error. I would like to check if I can reliably call the Quit() function.

SGaist

What other methods are available in this Application object ?

Maxbester

It has many but all will fail if the connection has not been set or if the connection is broken. I think the QMetaObject class shall have a method that tests the establishment of a connection.

Hasn't anyone faced this problem before?

SGaist

That's a question you should ask on the interest mailing list, you'll find Qt's developers/maintainers there (this forum is more user oriented)

Maxbester

Okay you're right.

Just an additional information.

I voluntarily generated an error while connecting to the QAxObject and I got those messages in the Qt Creator console:

@
CoCreateInstance failure (The class has not a valid license.)

QAxBase::setControl: requested control {587b4a33-81d3-11cf-91c5-0020af429815} could not be instantiated

QAxBase::qt_metacall: Object is not initialized, or initialization failed
@

So some messages are emitted. The question is how to catch them...

SGaist

Maybe the QAxBase::exception signal ?