Possible bug in int64_t values XDR encoding?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Possible bug in int64_t values XDR encoding?

Jorge Santos Simón
Hello all,

I have realized that uint64_t values sent by player contains two
identical integers, one in the 4 high bytes and one in the low ones.

I supose this is an error. Has anyone noticed that?

regards,
Jorge

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Playerstage-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/playerstage-developers
Reply | Threaded
Open this post in threaded view
|

Re: Possible bug in int64_t values XDR encoding?

Rich Mattes-2
> -----Original Message-----
> From: Jorge Santos Simón [mailto:[hidden email]]
> Sent: Friday, July 15, 2011 4:46 PM
> To: [hidden email]
> Subject: [Playerstage-developers] Possible bug in int64_t values XDR
> encoding?
>
> Hello all,
>
> I have realized that uint64_t values sent by player contains two
> identical integers, one in the 4 high bytes and one in the low ones.
>
> I supose this is an error. Has anyone noticed that?
>
> regards,
> Jorge
>

It's probably an error, and it's definitely possible nobody has ever
noticed.  There's only one interface that has any 64-bit ints in a data
structure (the health interface,) and even then it looks like that
particular structure isn't mapped to any requests or commands anyway.  Does
everything look ok in the generated xdr functions?

Rich


------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Playerstage-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/playerstage-developers
Reply | Threaded
Open this post in threaded view
|

Re: Possible bug in int64_t values XDR encoding?

Jorge Santos Simón
In reply to this post by Jorge Santos Simón
I think that the error comes from the fact that a long int in a
32-bits machine like mine has only 4 bytes, and not 8 as expected.

So I guess that the type int64_t should be a long long int.


> It's probably an error, and it's definitely possible nobody has ever
> noticed.  There's only one interface that has any 64-bit ints in a data
> structure (the health interface,) and even then it looks like that
> particular structure isn't mapped to any requests or commands anyway.  Does
> everything look ok in the generated xdr functions?
>
> Rich

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Playerstage-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/playerstage-developers