Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 669
    • Issues 669
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 351
    • Merge requests 351
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #164

Closed
Open
Created Mar 28, 2016 by Bugzilla Migration User@bugzilla-migration

structure: Large integer gets detected as double instead of int64

Submitted by Vivia Nikolaidou @vivia

Link to original bug (#764288)

Description

Created attachment 324893
Test case

Running the attached test case gives this output:

Serialized structure measurement, field1=(int)1000000000;
Structure didn't contain an int64 field1
Serialized structure measurement, field1=(double)10000000000;
Structure didn't contain an int64 field1

Why double? There's no decimal point anywhere, shouldn't it be detected as an int64 instead?

PS: I know it's leaky, it's just a small demo.
PS2: Why is there no GST_STRUCTURE_FORMAT ? Now I'm leaking the strings as well as the structures :(

Attachment 324893, "Test case":
serializeme.c

Assignee
Assign to
Time tracking