From mjacob@quarm.feral.com Fri May  7 10:15:53 1999
Return-Path: <mjacob@quarm.feral.com>
Received: from quarm.feral.com (quarm.feral.com [192.67.166.252])
	by hub.freebsd.org (Postfix) with ESMTP id 6B9DA14D6D
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  7 May 1999 10:15:47 -0700 (PDT)
	(envelope-from mjacob@quarm.feral.com)
Received: (from mjacob@localhost)
	by quarm.feral.com (8.9.3/8.8.8) id KAA48903;
	Fri, 7 May 1999 10:15:47 -0700 (PDT)
	(envelope-from mjacob)
Message-Id: <199905071715.KAA48903@quarm.feral.com>
Date: Fri, 7 May 1999 10:15:47 -0700 (PDT)
From: Matthew Jacob <mjacob@quarm.feral.com>
Reply-To: mjacob@quarm.feral.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: tar verification doesn't work
X-Send-Pr-Version: 3.2

>Number:         11562
>Category:       gnu
>Synopsis:       tar verification doesn't work
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May  7 10:20:01 PDT 1999
>Closed-Date:    Thu Aug 22 10:16:41 PDT 2002
>Last-Modified:  Thu Aug 22 10:16:41 PDT 2002
>Originator:     Matthew Jacob
>Release:        FreeBSD 4.0-CURRENT i386
>Organization:
Feral Software
>Environment:

4.0 currrent as of 5/7/1999.


>Description:

Tar with verification is broken.

If you try and verify a tape file, it's broken because it closes the tape
file (causing a filemark to be written) but only does one BSF- it doesn't
relocate to the front of the tape file just written.

If you try and verify a regular file, you get the diagnostice:

quarm.feral.com > tar --create --verify --file /tmp/foo.tar .
tar in free(): warning: chunk is already free.


>How-To-Repeat:

Try verification.

>Fix:
	
	


>Release-Note:
>Audit-Trail:

From: Duncan Idaho <sydney13@mail.com>
To: freebsd-gnats-submit@FreeBSD.org, mjacob@quarm.feral.com
Cc:  
Subject: Re: gnu/11562: tar verification doesn't work
Date: Tue, 23 Jan 2001 21:48:38 +0100

 I've the same problem with tar under 5.0 CURRENT.
 
 Here is the output from a backtraced core dump:
 
 # uname -a
 FreeBSD soleil 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jan 22 01:51:40
 CET 2001     root@soleil:/usr/src/sys/compile/URANUS  i386
 # /usr/obj/usr/src/gnu/usr.bin/tar/tar --verify -cf ports.tar
 ports/Makefile
 tar in free(): error: junk pointer, too high to make sense.
 Abort (core dumped)
 # gdb -core tar.core /usr/obj/usr/src/gnu/usr.bin/tar/tar
 GNU gdb 4.18
 Copyright 1998 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for
 details.
 This GDB was configured as "i386-unknown-freebsd"...
 Core was generated by `tar'.
 Program terminated with signal 6, Abort trap.
 #0  0x808a868 in kill ()
 (gdb) bt
 #0  0x808a868 in kill ()
 #1  0x8089c7a in abort () at /usr/src/lib/libc/../libc/stdlib/abort.c:71
 #2  0x8088a85 in wrterror (
     p=0x8099120 "junk pointer, too high to make sense.\n")
     at /usr/src/lib/libc/../libc/stdlib/malloc.c:293
 #3  0x8088aa4 in wrtwarning (
     p=0x8099120 "junk pointer, too high to make sense.\n")
     at /usr/src/lib/libc/../libc/stdlib/malloc.c:301
 #4  0x8089459 in ifree (ptr=0xbfbffcdc)
     at /usr/src/lib/libc/../libc/stdlib/malloc.c:1046
 #5  0x8089999 in free (ptr=0xbfbffcdc)
     at /usr/src/lib/libc/../libc/stdlib/malloc.c:1101
 #6  0x8050e57 in read_header () at /usr/src/gnu/usr.bin/tar/list.c:411
 #7  0x804c6a9 in verify_volume () at
 /usr/src/gnu/usr.bin/tar/diffarch.c:521
 #8  0x8049ce5 in close_archive () at
 /usr/src/gnu/usr.bin/tar/buffer.c:1255
 #9  0x804a5b5 in create_archive () at
 /usr/src/gnu/usr.bin/tar/create.c:178
 #10 0x8052c9d in main (argc=5, argv=0xbfbffba8)
     at /usr/src/gnu/usr.bin/tar/tar.c:240
 #11 0x8048135 in _start ()
 (gdb) quit
 
 $FreeBSD: src/lib/libc/stdlib/malloc.c,v 1.55 2000/12/09 09:35:32 obrien
 Exp $
 $FreeBSD: src/gnu/usr.bin/tar/tar.c,v 1.23 2000/12/24 10:52:23 obrien
 Exp $
 
State-Changed-From-To: open->suspended 
State-Changed-By: mike 
State-Changed-When: Fri Jul 20 08:58:32 PDT 2001 
State-Changed-Why:  

Awaiting fix and committer. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=11562 
State-Changed-From-To: suspended->patched 
State-Changed-By: sobomax 
State-Changed-When: Tue Jun 4 10:59:23 PDT 2002 
State-Changed-Why:  
Modern GNU tar which was just imported into the -CURRENT doesn't have this 
problem. Therefore, the problem will befilly resolved when tar upgrade is 
MFC'ed in about 1 month. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=11562 
State-Changed-From-To: patched->closed 
State-Changed-By: johan 
State-Changed-When: Thu Aug 22 10:16:21 PDT 2002 
State-Changed-Why:  
GNU tar 1.13.25 has been MFCed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=11562 
>Unformatted:
