From owner-freebsd-questions@FreeBSD.ORG Tue Feb 21 22:54:51 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A7016A422 for ; Tue, 21 Feb 2006 22:54:51 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6085D43D45 for ; Tue, 21 Feb 2006 22:54:51 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.4/8.13.4) with ESMTP id k1LMsol6010124 for ; Tue, 21 Feb 2006 14:54:50 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.4/8.13.4/Submit) with UUCP id k1LMsokl010121 for freebsd-questions@freebsd.org; Tue, 21 Feb 2006 14:54:50 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id WAA03728; Tue, 21 Feb 2006 22:50:30 GMT Message-Id: <200602212250.WAA03728@sopwith.solgatos.com> To: freebsd-questions@freebsd.org Date: Tue, 21 Feb 2006 14:50:30 +0000 From: Dieter Subject: Re: tar segmentation fault X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2006 22:54:51 -0000 > When source/usr/home/me/public_html is empty then it runs fine. But when I put > any links in, tar dies with a segmentation fault. > > Has anyone got any ideas why? > Yup, looks like I'm using bsdtar Now that you know which tar you're using, :-) time to drag out the standard debugging process for segmentation faults. 1) get the sources 2) compile, adding "-g" 2a) If you get any compiler warnings, fix them and send the diffs to the maintainer. Often fixing the compiler warnings will fix a seg fault. 3) Try it again. If it still seg faults, run it under a debugger and get a stack backtrace.