mclIsMCRInitialized crashes if mclInitializeApplication not yet called

mclIsMCRInitialized crashes if mclInitializeApplication has not been called. It returns 1, as expected, if mclInitializeApplication has been called.

I know mclInitializeApplication is supposed to be the first function called to initialize the MCR, but surely mclIsMCRInitialized should behave sanely (and return 0) rather than crash. What am I missing?

Answer 1

[Titus Edelhofer]

Hi Guy,

from my personal view I guess you are missing nothing. I will ask our development to look into this ...

Titus

[Guy]

Thanks Titus,

I get the same behaviour on both a 64-bit Linux and 32-bit Windows.

Answer 2

[Guy]

I've checked this using 2011b on Linux now and with the same outcome.

Answer 3

[Benjamin Guinot]

Hi,

I have the same problem (32-bit Windows). Have you made any progress on this problem?

Thank you

Ben

[Guy]

No, Ben.

Just don't use it.

Answer 4

[Friedrich]

Hi,

the problem here is that the proxy library has not been initialized. To initialize these libraries call:

mclmcrInitialize()

first. This will NOT start the MCR, it simply initializes the libs so the call to mclIsMCRInitialized doesnt crash anymore. As far as I know this command is save. You can call it as often as you want and it doesnt need the MCR running.

(This command isnt documented but used in the matrixdriver example)