[ace-users] ACE TAO: Upgrade from 5.5.4 to 6.5.7

[Yorick]

Hi All,

Just to give an update so this issue can be closed.

We figured out after investigation that there must be a bug in the Intel
Compiler we are using.
Reducing the optimization from -O3 to -O2 solved this issue.

--- ACE_wrappers/include/makeinclude/platform_linux_icc.GNU Fri Nov 22
09:26:59 2019
+++ ACE_wrappers/include/makeinclude/platform_linux_icc.GNU Fri Mar 13
13:07:57 2020
@@ -84,7 +84,7 @@
   LIBS += -lrt
 endif

-OCFLAGS += -O3
+OCFLAGS += -O2

 # Disable floating point optimizer solves problem with
 # min/max float values in the TAO_IDL compiler tests

I hope this helps anyone encountering the same issue.

Many thanks for the quick responses.

Yorick Bosman

Op do 12 mrt. 2020 om 17:02 schreef Yorick <yorick.bosman at gmail.com>:

> Hi Johnny and Adam,
>
> Thanks for the quick reply.
> With valgrind I could eventually found out an issue with ACE / our code
> (not sure where the responsibility lies)
>
> So, the issue is when we call CORBA::ORB_init with some strange variables:
>
> char* argv[5];
> argv[0] = "argument0";
> argv[1] = "argument1";
> argv[2] = "argument2";
> argv[3] = "argument3";
> argv[4] = "argument4";
>
> int argc = 3;
>
> // The issue occurs here, argv has more values after the count of 3
> (specified by argc)
> CORBA::ORB_init ( argc, argv, "something" );
>
> When I force argv[3][0] = "\0"; it seems to work, although i get an other
> issues somewhere else.
>
> To be complete: everything works just fine with ACE 5.5.4. Unit tests seem
> to work just fine.
>
> Regards,
> Yorick
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.isis.vanderbilt.edu/pipermail/ace-users/attachments/20200316/2b7e6a45/attachment.html>