Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

pkgin upgrade and pkgin install segfault #94

Closed
ghost opened this issue Aug 9, 2020 · 1 comment
Closed

pkgin upgrade and pkgin install segfault #94

ghost opened this issue Aug 9, 2020 · 1 comment
Assignees

Comments

@ghost
Copy link

ghost commented Aug 9, 2020

On a recent upgraded NetBSD amd64 system from 9.99.64 to 9.99.69 I get segfaults for pkgin upgrade and for some packages with pkgin install.

Here are the files for analysis:

irc snip

21:13 <nikita`> for a package which exists:
21:13 <nikita`> pkgin install python38
21:13 <nikita`> calculating dependencies...done.
21:13 <nikita`> [1]   Segmentation fault (core dumped) pkgin install python38
21:13 <nikita`> for upgrade:
21:13 <nikita`>  pkgin upgrade
21:13 <nikita`> calculating dependencies...done.
21:13 <nikita`> [1]   Segmentation fault (core dumped) pkgin upgrade
@ghost ghost changed the title pkgin upgrade, pkgin install, segfaults pkgin upgrade and pkgin install segfault Aug 9, 2020
@ghost
Copy link
Author

ghost commented Aug 9, 2020

backtrace, without debug symbols:

[New process 23255]
Core was generated by `pkgin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000077f8f2584870 in strlen () from /usr/lib/libc.so.12
(gdb) bt
#0  0x000077f8f2584870 in strlen () from /usr/lib/libc.so.12
#1  0x000077f8f24b17be in _strdup (str=0x0) at /usr/src/lib/libc/string/strdup.c:60
#2  0x000000000040db82 in xstrdup ()
#3  0x0000000000407d36 in order_install ()
#4  0x0000000000404faf in pkgin_install ()
#5  0x0000000000405ab6 in pkgin_upgrade ()
#6  0x00000000004156b1 in main ()

@jperkin jperkin self-assigned this Aug 10, 2020
jperkin pushed a commit that referenced this issue Aug 28, 2020
This isn't actually supported at present, but I want some time to create
proper test cases and handle everything correctly, so for now we punt
and ignore removals which is how pkgin behaved prior to 20.7.0.

Apologies for the crashes, but in my defence it exposed a real bug,
which was the reason for removing the checks in the first place.

Should "fix" #94, and reports via private message.
@jperkin jperkin closed this as completed Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant