Debian bug report logs - #1102
tar v 1.11.8 gives a segmentation fault error

Message received at debian-bugs:

From fea.rrd.ornl.gov!fea Fri Jul 14 14:38:04 1995
Return-Path: <fea@fea.rrd.ornl.gov>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sWsQu-0005TtC; Fri, 14 Jul 95 14:38 PDT
Received: from fea.rrd.ornl.gov by pixar.com with SMTP id AA09785
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 14 Jul 1995 14:36:33 -0700
Received: by fea.rrd.ornl.gov
	id <m0sWsQs-0000W4C@fea.rrd.ornl.gov>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Fri, 14 Jul 95 17:38 EDT
Message-Id: <m0sWsQs-0000W4C@fea.rrd.ornl.gov>
Date: Fri, 14 Jul 95 17:38 EDT
From: fea@fea.rrd.ornl.gov (James D. Freels)
To: debian-bugs@pixar.com
Subject: tar v 1.11.8 gives a segmentation fault error 

The newest version of tar gives me a segmentation fault error
when I use it to create remote archives.  The error only occurs
when I create an archive remotely and did not occur on the 
previous version of tar.  The command I use is

tar cvfX vicws:/dev/rmt0 exclude_files / 2>backup_all.error | tee backup_all.list

but it is only necessary to do the following command

tar cvf vicws:/dev/rmt0 /root 

to produce the error.

I tried to rebuild the same version of tar from scratch off of the
sunsite archive and was not able to do so.  I'm going to try to
copy an old debian-distribution copy from my personal archive to
see if the error is still present.  The error occurs on additional
remote machines besides vicws.  The error occurs immediately.

I will let you know if a previous version fixes the problem.

-- 
[]----------------------------------------------------------------[]
| James D. Freels, P.E., Ph.D.    | Phone:  (615) 576-8645     | L |
| Oak Ridge National Laboratory   | FAX:    (615) 574-9172     | I |
| Research Reactors Division      | Internet: fea@ornl.gov     | N |
| P. O. Box 2008                  | Reactor Technology Section | U |
| Oak Ridge, Tennessee 37831-6392 | the world's best neutrons! | X |
[]----------------------------------------------------------------[]

Your message didn't have a Package: line at the start (in the pseudo-header following the real mail header), or didn't have a psuedo-header at all.

This makes it much harder for us to categorise and deal with your problem report; please ensure that you say which package(s) and version(s) the problem is with next time. Some time in the future the problem reports system may start rejecting such messages.

Full text available.