Re: Possible bug in int64_t values XDR encoding?
Jorge Santos Simón <[email protected]>
| Newsgroups | gmane.science.robotics.playerstage |
|---|---|
| Message-ID | <CABpbO7o9ObXhDMDY0rnX6BFGHQbocXaj4bxcobk7i+hSC-cAMw@mail.gmail.com> |
Yes, declaring int64_t as long long int solves the problem for 32 bits architectures. I have submitted a patch. Thanks > 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 ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev