[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#732937: dpkg: fails somewhat regularly on kfreebsd-amd64



On 20:05, Steven Chamberlain wrote:
> I think this is the interesting part:

Something interesting happened before that, too.  I was trying to
update the 'gzip' package:

2014-01-12 19:57:56 status unpacked gzip:kfreebsd-amd64 1.6-3
2014-01-12 19:57:57 status half-configured gzip:kfreebsd-amd64 1.6-3
2014-01-12 19:57:58 status installed gzip:kfreebsd-amd64 1.6-3

but dpkg had a problem with stdout prior to that:

  6637 dpkg     CALL  open(0x758980,0<O_RDONLY>,<unused>0)
  6637 dpkg     NAMI  "/var/lib/dpkg/diversions"
  6637 dpkg     RET   open 7
  6637 dpkg     CALL  fcntl(0x7,<invalid=1>,0)
  6637 dpkg     RET   fcntl 0
  6637 dpkg     CALL  fcntl(0x7,<invalid=2>,FD_CLOEXEC)
  6637 dpkg     RET   fcntl 0
  6637 dpkg     CALL  fstat(0x7,0x7fffffffcbd0)
  6637 dpkg     STRU  invalid record
  6637 dpkg     RET   fstat 0
  6637 dpkg     CALL  mmap(0,0x4000,0x3<PROT_READ|PROT_WRITE>,0x1002<MAP_ANON|MAP_TYPE|MAP_PRIVATE>,0xffffffff,0)
  6637 dpkg     RET   mmap 34368126976/0x800800000
  6637 dpkg     CALL  read(0x7,0x800800000,0x4000)
  6637 dpkg     GIO   fd 7 read 417 bytes
    [...]
  6637 dpkg     RET   read 417/0x1a1
  6637 dpkg     CALL  read(0x7,0x800800000,0x4000)
  6637 dpkg     GIO   fd 7 read 0 bytes
       ""
  6637 dpkg     RET   read 0
  6637 dpkg     CALL  break(0x9b4000)
  6637 dpkg     RET   break 0
  6637 dpkg     CALL  write(0x1,0x7fffffffaaf0,0x1c)
  6637 dpkg     RET   write -1 errno 6 No such device or address

and an error message about this subsequently fails to go to stderr:

  6637 dpkg     CALL  fcntl(0x5,<invalid=1>,<invalid>0x753e20)
  6637 dpkg     RET   fcntl 1
  6637 dpkg     CALL  fcntl(0x5,<invalid=2>,FD_CLOEXEC)
  6637 dpkg     RET   fcntl 0
  6637 dpkg     CALL  fcntl(0x5,<invalid=9>,0xffffffffffffd120)
  6637 dpkg     RET   fcntl 0
  6637 dpkg     CALL  stat(0x753e20,0x7fffffffd0d0)
  6637 dpkg     NAMI  "/var/lib/dpkg/triggers/Unincorp"
  6637 dpkg     STRU  invalid record
  6637 dpkg     RET   stat 0
  6637 dpkg     CALL  fcntl(0x5,<invalid=8>,0xffffffffffffd110)
  6637 dpkg     RET   fcntl 0
  6637 dpkg     CALL  open(0x753d80,0<O_RDONLY>,<unused>0)
  6637 dpkg     NAMI  "/usr/share/locale/en_GB/LC_MESSAGES/libc.mo"
  6637 dpkg     RET   open -1 errno 2 No such file or directory
  6637 dpkg     CALL  open(0x7681d0,0<O_RDONLY>,<unused>0)
  6637 dpkg     NAMI  "/usr/share/locale/en/LC_MESSAGES/libc.mo"
  6637 dpkg     RET   open -1 errno 2 No such file or directory
  6637 dpkg     CALL  write(0x2,0x7fffffffa560,0x6c)
  6637 dpkg     RET   write -1 errno 6 No such device or address
  6637 dpkg     CALL  write(0x2,0x800bb70a3,0x1)
  6637 dpkg     RET   write -1 errno 6 No such device or address
  6637 dpkg     CALL  write(0x10,0x75b500,0x57)
  6637 dpkg     GIO   fd 16 wrote 87 bytes
       "status: gzip : error : error writing to '<standard output>': No such file or directory
       "
  6637 dpkg     RET   write 87/0x57
  6637 dpkg     CALL  open(0x75b6a0,0x601<O_WRONLY|O_CREAT|O_TRUNC>,0x1b6<><invalid>438)
  6637 dpkg     NAMI  "/var/lib/dpkg/status-new"
  6637 dpkg     RET   open 8

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org


Reply to: