Skip to content

Can overflow occur when reading unsigned int32 ? #19

@GoogleCodeExporter

Description

@GoogleCodeExporter
What steps will reproduce the problem?
1. bitmatch this: 
{ im: 32: littleendian } 

Works fine for some values and not for others

What is the expected output? What do you see instead?
An unsigned int32 is expected But a signed int32 is given.
I also tried putting the attribute unsigned, but it didn't change anything

What version of the product are you using? On what operating system?
I'm using version 2.0.3 on Ubuntu 12.04

Please provide any additional information below.


Original issue reported on code.google.com by josephel...@gmail.com on 7 Jun 2012 at 3:06

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions