I solved the problem.
The OPTIMIZE option in config/Make.rules needs to be selected.
With that option, my server stop crashing after two tries! I can use it as long as I want !!
Thank you !!
|
|
I solved the problem.
The OPTIMIZE option in config/Make.rules needs to be selected.
With that option, my server stop crashing after two tries! I can use it as long as I want !!
Thank you !!
-----------------
Arnaud
ENSEIRB Student
Bordeaux
Hi Arnaud,
I don't think it solved your problem, the assert() from the IceUtil::Mutex::~Mutex destructor is just not triggered anymore because assert() only works for debug builds. The mutex destruction still most likely fails. I don't know if this will cause any other problems but it would be good to find the reason why you get this assert.
When you built Ice *without* OPTIMIZE enabled, did you try to run the test suite? Does all the tests pass? You can run the test suite with the "./allTests.py" script at the top level of your Ice source distribution.
Cheers,
Benoit.
Hi Benoit,
This time I think I may find the problem.
My TX board is a 64 bits microprocessor (one of my colleague told me that today. But I should have read the datasheet before !!!!) .But I always compiled ICE for 32 bits.
I compiled ICE with 64 bits and without OPTIMIZE mode.
The server is running without problem. No crash !!!
About the tests, all is OK !!
Thank you very much !!
-----------------
Arnaud
ENSEIRB Student
Bordeaux
There are currently 1 users browsing this thread. (0 members and 1 guests)