Re: Possible Bug in 3.14.9 Access Security on mv2100

[Kay-Uwe Kasemir <kasemirk@ornl.gov>]

On Aug 17, 2007, at 08:39 , Dirk Zimoch wrote:

> Ralph,
>
> that's probably not the only CA problem in 3.14.9.
> In May, I repored a bug to the Mantis bugtracker which has not even  
> been assigned until now. (Maybe posting it to tech-talk helps.)
>
> > Summary long integer values are corruped in R3.14.9
> > Description
> > When writing integer values with a CA client (e.g. medm) to a long  
> > integer channel (e.g. longout record), the upper bytes get  
> > corrupted. The lower 2 bytes are OK.
> > I can't see the error when the client is caput from base.
> > Client and IOC run on a linux-x86 machine.
> > The problem is new in 3.14.9.

Could that be related to this byte swapping issue in the known problems:
"G++ version 3.2.3
Jeff Hill reports the following:

During testing of R3.14.9 I see a bug showing up only in optimized  
builds on Linux using g++ 3.2.3 that I don't see with other  
compilers. This bug appears to be related to failure of this  
particular compiler to follow the strict alias rules specified in the  
standard when optimizing the byte swapping templates installed for  
R3.14.9.

Problems
Red hat Linux g++ 3.2.3 when -O3 is specified
"

?

-Kay