Please report new issues athttps://github.com/DOCGroup
Here is a valid report from Malcolm. ----------------------------------------------------------------------------------- TAO VERSION: 1.4.1 ACE VERSION: 5.4.1 HOST MACHINE and OPERATING SYSTEM: Pentium 4, Debian linux TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): g++ (GCC) 3.3.4 (Debian 1:3.3.4-13) AREA/CLASS/EXAMPLE AFFECTED: AMH DOES THE PROBLEM AFFECT: COMPILATION? no LINKING? no EXECUTION? yes OTHER (please specify)? SYNOPSIS: When calling an AMH servant from a proxy within the same process, the proper servant method is called, but the data passed into the parameters is bad. DESCRIPTION: It appears that the TAO option to perform direct function calls for colocated objects isn't compatible with AMH servants. The same call works ok with -ORBCollocation no. We'd still like to be able to use this feature with non-AMH servants. Can we mix these 2 safely? Are we going to have the same problem with AMI? REPEAT BY: Make any call on an AMH object from within the same process. SAMPLE FIX/WORKAROUND: Run with -ORBCollocation no . -- +-----+ |SPEED| "It's not just a good idea, it's the law" | | - Albert Einstein (paraphrased) | c | | | |LIMIT| +-----+
When Ossama works on AMH in skeleton refactoring this needs to be taken care off.
Mine.
Ossama, is this addressed with the skeleton refactoring?
added blocks
We're having the same problem with AMI (on vers 1.4.2). A colocated AMI call that assigns a value to an out parameter causes a segmentation fault.
accept, still valid with 1.5.2
changed component to AMH
updated version