On Tue, Dec 17, 2002 at 06:33:04PM +1100, Tim Robbins wrote:
> On Tue, Dec 17, 2002 at 01:44:44AM +0100, Riccardo Torrini wrote:
> 
> > Trying to extract a single or multi volume archive doesn't work.
> > Same archive can be extracted fine with unrar under 4.7-STABLE.
> > My -CURRENT from 10 day ago.  Tryed to remove and rebuild unrar
> > without luck.  rar on -CURRENT also works.  Any idea?
> [...]
> > # uname -v
> > FreeBSD 5.0-RC #47: Sun Dec  8 18:09:42 CET 2002 ...
> > 
> > # unrar t sample.rar 
> > 
> > UNRAR 3.10 beta 1 freeware      Copyright (c) 1993-2002 Eugene Roshal
> > 
> > Cannot open sample.rar
> > No files to extract
> [...]
> 
> I tried to reproduce this but could not with these two versions of unrar:
> 
> UNRAR 3.00 freeware (from source)
> UNRAR 3.10 beta 1 freeware (from ports)
> 
> The output of ktrace/kdump or truss would be useful in investigating this.

It fails on ref5:

[~/ports/archivers/unrar] edwin@ref5>work/unrar/unrar t ../rar/sample.rar 

UNRAR 3.10 beta 1 freeware      Copyright (c) 1993-2002 Eugene Roshal

Cannot open ../rar/sample.rar
No files to extract

[~/ports/archivers/unrar] edwin@ref5>


Think it has something to do with this one:
 46353 unrar    CALL  open(0xbfbf98e3,0,0xbef6d8)
 46353 unrar    NAMI  "../rar/sample.rar"
 46353 unrar    RET   open 3
 46353 unrar    CALL  flock(0x3,0x6)
 46353 unrar    NAMI  "/var/run/lock"
 46353 unrar    RET   flock -1 errno 45 Operation not supported
 46353 unrar    CALL  close(0x3)
 46353 unrar    NAMI  "/var/run/lock"
 46353 unrar    RET   close 0
 46353 unrar    CALL  write(0x2,0xbfbed670,0x1e)
 46353 unrar    GIO   fd 2 wrote 30 bytes
       "
        Cannot open ../rar/sample.rar"

That's in file.cpp:73, LOCK_EX is in /usr/include/fcntl.h
Haven't looked at the rest.

Edwin

-- 
Edwin Groothuis      |            Personal website: http://www.MavEtJu.org
[EMAIL PROTECTED]    |    Weblog: http://www.mavetju.org/weblog/weblog.php 
bash$ :(){ :|:&};:   | Interested in MUDs? http://www.FatalDimensions.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to