bugCERTI - Bugs: bug #19869, registerObjectInstanceWithRegion...

 
 

bug #19869: registerObjectInstanceWithRegion BUG

Submitter:  moosefly <moosefly>
Submitted:  Sun 13 May 2007 02:35:08 PM UTC
 
Category:  CERTI Severity:  * 3 - Normal
Item Group:  Software error Status:  None
Privacy:  Public Assigned to:  erk
Open/Closed:  Open Release:  * 3.2.3
Reproducibility:  Every Time Fixed Release:  * Unknown
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Tue 04 Sep 2007 08:32:14 AM UTC, comment #1: 

I've just dive into the code for a while
and I agree this seems to be a bug.
We should certainly loop over "req->regions".

The fact is in the NetworkMessage class there is both:

req->region  (coming from NetworkMessage::region)
req->regions (coming from BasicMessage::regions)

I do not know this part of CERTI [yet :)]
so I need to understand the role of

NetworkMessage::region

vs

BasicMessage::regions

in order to find a precise answer and fix for this.

However this work is currently not very high in
my CERTI work stack.
Is this 'blocking' for your CERTI usage?

Do you you have a test case which exhibit a wrong behavior?

Did you try a patch on your side?

Eric NOULARD <erk>
Project Administrator
Sun 13 May 2007 02:35:08 PM UTC, original submission:  

RTI::ObjectHandle
RTI::RTIambassador::registerObjectInstanceWithRegion(
ObjectClassHandle object_class,
const char *tag,
AttributeHandle attrs[],
Region *regions[],
ULong nb)

We can see that the "regions" parameter include multi regions, and certi use "build_region_handles" function to transform it to the RegionHandle array. But the RTIG did not process the RegionHandle array correctly:

In RTIG_processing.cc

// ----------------------------------------
// processRegisterObjectWithRegion
void
RTIG::processRegisterObjectWithRegion(Socket link, NetworkMessage req)
{
    NetworkMessage rep ;
    rep.object = federations.registerObjectWithRegion(req->federation,
req->federate,
req->objectClass,
req->label,
req->region,
^^^^^^^^^^^
req->handleArraySize,
req->handleArray);

......
}

As shown, RTIG only get the "region" but not the "regions".In my opinion, it's a bug.

moosefly <moosefly>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one

Digest:
   task dependencies.

 

Carbon-Copy List
  • -email is unavailable- added by breholee
  • -email is unavailable- added by erk (Posted a comment)
  • -email is unavailable- added by moosefly (Submitted the item)
  •  

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-05-28 breholee Carbon-Copy- Added breholee
    2007-09-04 erk Dependencies- task #6904 is dependent
    2007-09-04 erk Assigned toNone erk

    Back to the top

    Powered by Savane 3.10