Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

pkg upgrade -v segfaults #1842

Open
ghost opened this issue May 26, 2020 · 4 comments · May be fixed by #1903
Open

pkg upgrade -v segfaults #1842

ghost opened this issue May 26, 2020 · 4 comments · May be fixed by #1903

Comments

@ghost
Copy link

ghost commented May 26, 2020

As below:

# pkg upgrade -nv
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
vulnxml file up-to-date
Checking for upgrades (21 candidates):  33%Child process pid=10544 terminated abnormally: Segmentation fault

I didn't know -v is for "vulnerable" as it's not documented and I was hoping it would give me more verbose output, but anyway.

Reading symbols from /usr/local/sbin/pkg...
[New LWP 101416]
Core was generated by `pkg upgrade -nv'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000000046e093 in pkg_jobs_process_remote_pkg ()
(gdb) bt
#0  0x000000000046e093 in pkg_jobs_process_remote_pkg ()
#1  0x000000000046dcfa in pkg_jobs_find_upgrade ()
#2  0x000000000046b0e3 in pkg_jobs_solve ()
#3  0x00000000002a1b15 in exec_upgrade ()
#4  0x000000000029b198 in main ()

I was tempted to look into fixing this, but I must admit that I don't understand this option completely -- is it supposed to show/upgrade only vulnerable packages? Something else?
@ceri
Copy link
Contributor

ceri commented Nov 3, 2020

I don't know why yet, but the call to pkg_rdeps on line 771 of libpkg/pkg_jobs.c causes this when the package being evaluated is pkg itself.

ceri added a commit to ceri/pkg that referenced this issue Nov 10, 2020
@ceri
Fix issue freebsd#1842.
2352cbb
@ceri
Copy link
Contributor

ceri commented Nov 10, 2020

I think pull request #1903 fixes this.

@igalic
Copy link

igalic commented Nov 11, 2020

I didn't know -v is for "vulnerable" as it's not documented and I was hoping it would give me more verbose output,

this seems should also be a priority

@ceri ceri linked a pull request Nov 12, 2020 that will close this issue
Open
@bapt
Copy link
Member

bapt commented Jul 1, 2024

I can't reproduce this one anymore, I would be tempted to mark it as over come by events

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix issue #1842; fix some typos. ceri/pkg
3 participants
@bapt @ceri @igalic