bugCERTI - Bugs: bug #19685, Message::setValue with length >...

 
 

bug #19685: Message::setValue with length > MAX_BYTES_PER_VALUE fails

Submitter:  Eric NOULARD <erk>
Submitted:  Tue 24 Apr 2007 01:52:45 PM UTC
   
 
Category:  CERTI Severity:  * 4 - Important
Item Group:  Software error Status:  Fixed
Privacy:  Public Assigned to:  erk
Open/Closed:  Closed Release:  * 3.2.3
Reproducibility:  Every Time Fixed Release:  * 3.3.0
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 24 Apr 2007 01:52:45 PM UTC, original submission:  

In the current CERTI implement there exists
some constants definition which statically size
buffers.

When a user application request to add an Attribute Value
whose size exceed MAX_BYTES_PER_VALUE he ends up with
an RTIInternal error:

Message::setValue too high length = 128


128 is the requested length which is greater than 80
i.e. the current MAX_BYTES_PER_VALUE value.

The trouble is that this constant is fixed at compile time
so that if you want to set a greater you need to recompile
CERTI :((

I've pushed MAX_BYTES_PER_VALUE up to 150 and I will work
on a more "dynamic" solution which should hopefully avoid
recompilation.


Eric NOULARD <erk>
Group administrator

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Carbon-Copy List
  • -email is unavailable- added by erk (Submitted the item)
  •  

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-07-02 erk StatusIn Progress Fixed
        Open/ClosedOpen Closed
        Fixed ReleaseUnknown 3.3.0
    2008-05-24 erk Dependencies- bugs #23329 is dependent
    2007-10-25 erk Dependencies- bugs #21399 is dependent
    2007-05-04 erk Fixed ReleaseNone Unknown
    2007-05-04 erk ReleaseNone 3.2.3

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code