Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
apk-tools
apk-tools
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • apk-toolsapk-tools
  • Issues
  • #1576

Closed
Open
Opened Jan 17, 2013 by Natanael Copa@ncopaOwner

apk upgrade segaults

It seems like current apk segfaults when I run apk ugprade

I can reproduce it on both x86 and x86_64.

Contents of /etc/apk/repositories:

http://nl.alpinelinux.org/alpine/edge/main
http://nl.alpinelinux.org/alpine/edge/testing
@v2.4 http://nl.alpinelinux.org/alpine/v2.4/testing

It didn’t make any difference if i remove the @v2.4 repo.

The backtrace:

[New LWP 4328]
Core was generated by `src/apk upgrade'.
Program terminated with signal 11, Segmentation fault.
#0  generate_changeset (changeset=0x5b3ab854, solution=0x0, db=0x5b3abadc, 
    solver_flags=<optimized out>) at src/solver.c:1439
1439        for (i = 0; i < solution->num; i++) {
(gdb) bt
#0  generate_changeset (changeset=0x5b3ab854, solution=0x0, db=0x5b3abadc, 
    solver_flags=<optimized out>) at src/solver.c:1439
#1  apk_solver_solve (db=db@entry=0x5b3abadc, 
    solver_flags=solver_flags@entry=1, world=world@entry=0xb994620, 
    solution=solution@entry=0x5b3ab858, changeset=changeset@entry=0x5b3ab854)
    at src/solver.c:1590
#2  0x08066c68 in apk_solver_commit (db=0x5b3abadc, 
    solver_flags=solver_flags@entry=1, world=0xb994620) at src/solver.c:2059
#3  0x0804e728 in upgrade_main (ctx=0xb97a470, db=0x5b3abadc, argc=0, 
    argv=0x5b3ac28c) at src/upgrade.c:125
#4  0x0804ab8b in main (argc=0, argv=0x5b3ac28c) at src/apk.c:496
(gdb) 

(from redmine: issue id 1576, created on 2013-01-17, closed on 2013-10-12)

  • Changesets:
    • Revision 4c08eca3 by Timo Teräs on 2013-04-29T13:14:57Z:
upgrade: handle solver failure gracefully

It is internal bug, but don't segfault on it. Fixes #1576.
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/apk-tools#1576