RE: [certi-dev] Size of Constants

[Gotthard,Petr]

More modifications might be necessary: the behaviour might depend
whether the values are transported as "reliable" or not. The unreliable
transport (UDP) will never transport more than slightly less than 65535,
so large values should be transported via TCP regardless reliable or
not. I'm not sure if this behaviour is implemented.


Petr

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Christian Stenzel
Sent: Monday, April 21, 2008 2:14 PM
To: CERTI-devel
Subject: [certi-dev] Size of Constants

Hello,

we want to use CERTI for a project in our research group.

One federate computes in each sim-loop a grid of 300x300 double values
(->270000 bytes) and sends this to another federate.

This worked with pRTI and DMSO RTI.

CERTI uses preprocessor defines to limit the size of certain values in
include/certi.hh (https://savannah.nongnu.org/bugs/?21399,
https://savannah.nongnu.org/bugs/?21423)

So, I manually changed the constant MAX_BYTES_PER_VALUE to the required
value (270000) and recompiler CERTI.

This leads to a segmentation violation when starting any federate.

Furhter on, I changed BUFFER_SIZE_DEFAULT to 270000+36.

The same error occurs.

Is there an upper limit for these values?

I've seen that the files
SocketTCP.hh, SocketUDP.hh and SocketUN.hh contain also different
preprocessor constants.

E.g. in SocketUN.hh a constant called SOCKUN_BUFFER_LENGTH is defined. 
The value
is 4096. The above comment says that the buffer size have to be as long
as any data ever received by the socket.

Have these constants something to do with that behaviour?








--
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel