Archived
This forum has been archived. Please start a new discussion on GitHub.
Problem with Hello world Example
Hi,
I'm discovering Ice FrameWork, and following the documentations, I try The hello World Example.
I've rebuilding Ice to have an Ice in Release mode.
I've followed step by step, the example ( printer.ice ). And when I execute the server it is ok, by the way, but the execution of client failed ( "The application has requested the runtime to terminate it in an usual way, contact...").
I found the line which failed, it is simply printer->printString("hello world!").
An idea?
Thanks
I'm discovering Ice FrameWork, and following the documentations, I try The hello World Example.
I've rebuilding Ice to have an Ice in Release mode.
I've followed step by step, the example ( printer.ice ). And when I execute the server it is ok, by the way, but the execution of client failed ( "The application has requested the runtime to terminate it in an usual way, contact...").
I found the line which failed, it is simply printer->printString("hello world!").
An idea?
Thanks
0
Comments
-
Have a look at this:
http://www.zeroc.com/faq/windowsLibraryMixup.html
A library mix-up as described in this FAQ is also the most common reason for an application to crash in release mode even though it works in debug mode.0 -
hum...
I make verifications on what libs I use to link and to execute... and all seem normal. :eek:
I tried to use a debug configuration, to have more clues on what is wrong... I linked with Iced.lib and IceUtild.lib. You can see what it makes, on the file attachment when I execute the client.
Once more, It fails on printString's call.
Have an Idea?0 -
Did you perhaps compile parts of your code without support for RTTI? See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/_pluslang_dynamic_cast_operator.asp0 -
Right. I've forgotten to add /GR option in compiler option. I 've done it.
But the client throw an exception. Bad exception.
I try to launch Debug mode, but nothing wrong, just an unknown exception.
I'm damned...0 -
Its most likely an access violation in your server. See this months connections FAQ.0
-
And the access violation is most likely caused due to a debug/release library mix-up...0