Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!munnari.oz.au!csc!ccadfa!usage!basser!ultima!hades!greyham
From: greyham@hades.OZ (Greyham Stoney)
Newsgroups: comp.sources.d
Subject: uncompress trashes file if SIGINT at hairy question.....
Keywords: damn, blast, darn the torpedoes, argh, Sys V, Compress 4.0
Message-ID: <462@hades.OZ>
Date: 16 Oct 89 18:44:59 GMT
Organization: Ausonics Pty Ltd, Sydney, Australia
Lines: 28

Well, I just had my version of uncompress *REMOVE* the long-awaited patches
that I'd been sent for another program; It seems like a nasty bug in
uncompress - here's what uncompress -V reports:

$Header: compress.c,v 4.0 85/07/30 12:50:00 joe Release $
Options: BITS = 16

Ok, firstly, is this the latest version?. If so, here's the scenario:

It's on System V (Interactive 386/ix; though I doubt it makes any difference;
it probably doesn't help any though....), and with 14 character filenames,
it's easy enough to have a compressed filename which is too long; hence the
uncompressed filename is the same as the compressed filename.

If you're on a tty, uncompress prompts:
[bigfile] already exists; do you wish to overwrite [bigfile] (y or n)?

Ok, so say you get nervous and hit CTRL-C: uncompress REMOVES THE FILE.
There is no record left, and no way to recover it. This scenario seems
easy enough to accidentally replicate - has anyone else noticed it, and
would the great keeper of the compress source consider looking at the
problem?

							Greyham.
-- 
/*  Greyham Stoney:                            Australia: (02) 428 6476  *
 *     greyham@hades.oz  - Ausonics Pty Ltd, Lane Cove, Sydney, Oz.      *
 *    TDMP/IP: Telepathic Direct Marketing Personel Interface Protocol   */