From owner-freebsd-questions Fri Jul 21 12:41:10 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by hub.freebsd.org (Postfix) with ESMTP id 2473337BE64 for ; Fri, 21 Jul 2000 12:41:01 -0700 (PDT) (envelope-from admin@chemcomp.com) Received: from hermes.chemcomp.com (ppp5913.qc.bellglobal.com [206.172.201.225]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id PAA00062 for ; Fri, 21 Jul 2000 15:45:10 -0400 (EDT) Received: from chemcomp.com (sky.chemcomp.com [192.1.1.62]) by hermes.chemcomp.com (Postfix) with ESMTP id 1A96E16824 for ; Fri, 21 Jul 2000 15:40:48 -0400 (EDT) Message-ID: <3978A6F6.55C3E578@chemcomp.com> Date: Fri, 21 Jul 2000 15:39:34 -0400 From: System Administrator Organization: Chemical Computing Group, Inc. X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Tar bug??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I was about to submit a PR when a doubt crossed my mind. Is this a bug or a "feature"? $ tar -f /home/backup/arch.tar -A -v -C /net /net/basil tar: Segmentation fault $ Curiously, no core is dumped, so I cannot really debug (?) the problem. How could I? Why isn't there a core anyways? Again, strangely: $ tar -f /home/backup/arch.tar -c -v -C /net /net/basil tar: Removing leading / from absolute path names in the archive. $ tar ft /home/backup/arch.tar net/basil $ tar -f /home/backup/arch.tar -A -v -C /net /net/basil tar: Segmentation fault $ What am I missing here? FreeBSD sky.chemcomp.com 4.0-RELEASE FreeBSD 4.0-RELEASE #7: Tue Jun 27 16:42:57 EDT 2000 root@sky.chemcomp.com:/usr/src/sys/compile/SKY i386 $ tar --version GNU tar version 1.11.2 $ Thanks, Antoine Beaupre System Administrator Chemical Computing Group, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message