From owner-freebsd-ports Sun Aug 25 9:47:37 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74F5237B400; Sun, 25 Aug 2002 09:47:34 -0700 (PDT) Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D53243E6E; Sun, 25 Aug 2002 09:47:34 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id 96EE03198CD; Sun, 25 Aug 2002 11:47:31 -0500 (CDT) Date: Sun, 25 Aug 2002 11:47:31 -0500 From: "David W. Chapman Jr." To: current@freebsd.org Cc: ports@freebsd.org Subject: pkg_version and no origin found == SEGFAULT Message-ID: <20020825164731.GA88696@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: current@freebsd.org, ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 4.6-STABLE i386 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org It seems when pkg_version hits an installed port that has no origin found it segfaults. I have found other people to verify that it segfaults for them too. DWhite seems to think that it may be pointer corruption in libc, specifically snprintf, fopen, strlcpy or strncpy Here is the backtrace Program received signal SIGSEGV, Segmentation fault. 0x28204e57 in strlcpy () from /usr/lib/libc.so.5 (gdb) bt #0 0x28204e57 in strlcpy () from /usr/lib/libc.so.5 #1 0x0804a003 in pkg_do (pkg=0x0) at /usr/src/usr.sbin/pkg_install/version/perform.c:169 #2 0x08049bfc in pkg_perform (indexarg=0x0) at /usr/src/usr.sbin/pkg_install/version/perform.c:71 #3 0x08049a45 in main (argc=1, argv=0xbfbffc0c) at /usr/src/usr.sbin/pkg_install/version/main.c:79 #4 0x08049879 in _start () Any help or guidance would be appreciated. It does seem that portupgrade -f the ports that cause this problem fixes it because the origin is created. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message