Summary: | ports-mgmt/pkg: Segfaults on armv7 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx <mafsys1234> | ||||
Component: | Individual Port(s) | Assignee: | freebsd-pkg (Nobody) <pkg> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | pkg | ||||
Priority: | --- | Flags: | koobs:
maintainer-feedback?
(pkg) |
||||
Version: | Latest | ||||||
Hardware: | arm64 | ||||||
OS: | Any | ||||||
See Also: | https://github.com/freebsd/pkg/issues/1834 | ||||||
Attachments: |
|
Description
xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx
2020-04-17 05:55:48 UTC
Thank you for your report. Without any information we are unable to resolve issues. Please re-open this issue at the upstream issue tracker: https://github.com/freebsd/pkg/issues providing at least the following: - Exact FreeBSD version (uname -a output) - Exact pkg version - Kernel configuration if not GENERIC - pkg version -v output - Summary and backtrace output of the segfault (Using gdb [1]) [1] https://www.freshports.org/devel/gdb/
Comment 2
xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx
2020-04-17 06:18:45 UTC
Created attachment 213481 [details]
GDB output backtrace of segfaulting pkg.
Comment 3
xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx
2020-04-17 06:23:06 UTC
I seem to have had this closed before I've even finished... Oh well. (In reply to JustIgnoreMe from comment #3) Please feel free to re-open the issue (ideally at the upstream link provided in comment 1) if the additional information can be provided.
Comment 5
xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx
2020-04-17 08:39:02 UTC
It's ok, no problems, I did open up a bug report on github.
Comment 6
xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx
2020-04-17 08:39:50 UTC
Bug report: https://github.com/freebsd/pkg/issues/1834 ^Triage: Re-open pending upstream issue resolution this has probably been fixed, the github issue has been closed as well. I can't reproduce anywhere, sorry I was long to reply and interract. |