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
  • util.c
Find file BlameHistoryPermalink
  • Allan McRae's avatar
    Use STRDUP for error checking in more places · 0eda92c5
    Allan McRae authored Apr 13, 2020
    
    
    Use STRDUP() over strdup() to catch memory allocation errors.
    
    There are still some instances of strdup left, but these are in functions
    that currently have no error path and would require a larger rework.
    
    Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
    0eda92c5