Re: ORBit-mt-0.5.3a, sequence buffer corruption

[Elliot Lee <sopwith redhat com>]

On Wed, 15 Nov 2000, Antti T Tuominen wrote:

> I'm aiming this mostly at Sebastian, buy I though that maybe others
> would like to know as well.
> 
> I'm using ORBit-mt-0.5.3a and found two bugs regarding octet
> sequences. I believe that the _maximum field in a sequence should be
> the allocated size of the _buffer, and the _length field is the used
> part of that buffer. I'm getting _maximum -values like 3210738884 on
> the server side immediately after a sequence is passed to a function
> as a parameter. Another issue is that sometimes the content of the
> _buffer gets corrupted as well. I put together a piece of code
> demonstrating the bugs, it is available at

Right now, _maximum just never gets touched - it is pretty irrelevant to
user-level code, since the only place it could matter is in
(de)marshalling, and ORBit doesn't pay attention to it there yet.

I will make sure to convince ORBit2 to set it, but your code shouldn't
really be reading _maximum anyways AFAICS.

-- Elliot
"The Pythagorean Theorem employed 24 words, the Lord's Prayer has 66 words,
Archimedes Principle has 67 words, the 10 Commandments have 179 words, the
Gettysburg Address had 286 words, the Declaration of Independence, 1,300 words and
finally the European Commission's regulation on the sale of cabbage: 26,911 words."