Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pygobject pygobject
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 303
    • Issues 303
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • pygobjectpygobject
  • Issues
  • #278
Closed
Open
Issue created Nov 20, 2018 by Tom Schoonjans@tschoonj

GHashTable with boxed types values segfaults

I've been playing around with gobject-introspection and pygobject for the last couple of weeks and I have run into my first real problem.

I have a method that returns a newly allocated GHashTable with key-type int and value-type some boxed type I defined. Everything works fine from C, but with pygobject I run into segfaults and weird behavior as soon as I try and get the values from the dictionary in python.

Is this fully supported? I am seeing that several unittests for hash tables are skipped and marked as broken...

Assignee
Assign to
Time tracking