Bug 164918 - zip with wildcard on directory with large files causes segmentation fault
Summary: zip with wildcard on directory with large files causes segmentation fault
Alias: None
Product: Fedora
Classification: Fedora
Component: zip
Version: 4
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2005-08-02 17:56 UTC by Rodre Ghorashi-Zadeh
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2005-08-04 11:51:02 UTC

Attachments (Terms of Use)

Description Rodre Ghorashi-Zadeh 2005-08-02 17:56:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Description of problem:
Using zip with wildcard on the contents of a directory that contains a large file (5.7 GB) causes a segmentation fault. If I zip the file on it's own I get:

zip /root/test.zip somelargefile.dat
        zip warning: file too large: (null)
        zip warning: name not matched: somelargefile.dat

but it appears that the file get zipped successfully.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Find a large file on your file system, in my case 5.7 GB
2. Try and zip it along with the contents of the directory it is in using: zip somefile.zip some-dir/*
3. Notice Segmentation fault.

Actual Results:  zip /root/test.zip some-dir/*
Segmentation fault

Expected Results:  I was hoping the contents of the directory, inclusing the large file would have been put into a zip archive.

Additional info:

 uname -a
Linux myhostyname.localdomain 2.6.12-1.1398_FC4smp #1 SMP Fri Jul 15 01:05:24 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux

Comment 1 Ivana Varekova 2005-08-04 11:51:02 UTC
Thank you for your notice.
This bug will be solved in the next upstream version (The new zip version 3.0
should contained large file support - see upstream info page
I update this package when this version will be released.
Ivana Varekova  

Note You need to log in before you can comment on or make changes to this bug.