Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P Pacman
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Filipe Laíns
  • Pacman
  • Repository
Switch branch/tag
  • pacman
  • lib
  • libalpm
  • handle.c
Find file BlameHistoryPermalink
  • Morgan Adamiec's avatar
    libalpm: fix alpm_option_set_assumeinstalled · 0a25548c
    Morgan Adamiec authored Jan 23, 2020 and Allan McRae's avatar Allan McRae committed Jan 28, 2020
    
    
    It looks like this function has never actually worked. The current list
    is never set to NULL after being freed. So the new deps were just
    appended to the already freed list, leading to a segfault.
    
    Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
    0a25548c