Date: Mon, 17 Feb 2020 22:30:08 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 244204] ports-mgmt/dialog4ports - Segmentation fault after upgrade to 13.x-currrent Message-ID: <bug-244204-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244204 Bug ID: 244204 Summary: ports-mgmt/dialog4ports - Segmentation fault after upgrade to 13.x-currrent Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: gad@FreeBSD.org CC: rum1cro@yandex.ru CC: rum1cro@yandex.ru Flags: maintainer-feedback?(rum1cro@yandex.ru) I have one virtual machine running 12.x: FreeBSD <my.host12.edu> 12.1-STABLE FreeBSD 12.1-STABLE r357988 VM-Gilead-1= 2x=20 amd64 I removed all ports, and reinstalled them. Most of them are compiled via portupgrade, with just a few brought in via 'pkg install'. I shutdown the VM, duplicated to a new VM, and then upgraded that VM to be running 13.x: FreeBSD <my.host13.edu> 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r357988: Sun F= eb 16 02:16:34 EST 2020=20=20=20=20 root@<my.host13.edu>:/usr/obj/usr/src/amd64.amd64/sys/VM-Gilead-13x amd64 I use portsnap to update all of its data, and it recommends that I do a 'pkg bootstrap -f' before doing anything else. So I do that. Later on I use 'pkg version -vL =3D' and discover there are several ports w= hich need to be upgraded. I start upgrading them, and (to make a long story sho= rt) I notice that if an 'config' dialog box comes up, that I sometimes see it followed by: `Segmentation fault (core dumped) =3D=3D=3D> Options unchanged' I think the core dump happens only if I did not change any options when that dialog box came up. I determined it was the program 'dialog4ports' which w= as core-dumping with the segmentation fault. I could 'cd' into the directory = for some port, do a 'make config', hit the enter key (thus approving the current options without changing any), and it would core-dump. To solve this, I did: `cd /usr/ports/ports-mgmt/dialog4ports make config && make make deinstall && make install make clean' After doing this, I see no more problems with segmentation faults when runn= ing dialog4ports. And if I copy the dialog4ports program from my 12.x system t= o my 13.x system, those segmentation faults will reappear. So far I have not noticed any problems with any other ports after moving fr= om 12.x to 13.x, but then there are many port-executables which I have not run since that upgrade. I considered removing all ports and rebuilding all of = them on 13.x, but I haven't had the time to just yet. Perhaps when the system notices that a major OS-level upgrade has occurred,= the 'pkg bootstrap -f' step should update 'dialog4ports' in addition to 'pkg' itself? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244204-7788>