OMEdit crashes after opening OMShell

[Martin Sjölund]

To reproduce:
Start OMEdit
Click OMShell
From OMShell, call list(). See that it returns "" (nothing loaded; another error since I am assuming OMEdit should have started with the same session as OMEdit used)
In OMC Logger: call list() => Crash, OMC communication lost

[Adeel Asghar]

OMShell is launched as an external process, it does not use the omc connected with OMEdit. OMCLogger is almost like OMShell.
Sending list() in OMClogger takes a long time but still works on my machine. However, try changing this line in OMCProxy.cpp, line number 207

static const char *argv[] = { "-ORBgiopMaxMsgSize", "10485760" };

increase the message size and see if it works. It think this messsage size works for windows but not for linux probably.

[Martin Sjölund]

Calling list() in OMShell works for me (takes a loooong time though). And it's initialized in the same way as OMEdit.

But why don't you start OMShell in the same OMC session as OMEdit though? I thought the whole point was to get a nice shell to play with the models you edit at the same time. Else, you can just launch OMShell from start-menu...

[Adeel Asghar]

Run OMShell send command
loadModel(Modelica)
loadModel(ModelicaServices)
list()

if it runs fine then something is wrong with OMEdit, since OMShell and OMEdit are using the same CORBA implementation.