Pedro Martelletto wrote:
> On Wed, Sep 13, 2006 at 10:46:17PM +0200, Han Boetes wrote:
> >  24912 fsck_ffs GIO   fd 4 wrote 32 bytes
> >        "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
> >  24912 fsck_ffs RET   write 16384/0x4000
> >  24912 fsck_ffs CALL  munmap(0x861e3000,0x4000)
> >  24912 fsck_ffs RET   munmap 0
> >  24912 fsck_ffs CALL  munmap(0x7fb46000,0x1000)
> >  24912 fsck_ffs RET   munmap 0
> >  24912 fsck_ffs CALL  munmap(0x7c747000,0x4000)
> >  24912 fsck_ffs RET   munmap 0
> >  24912 fsck_ffs CALL  close(0x3)
> >  24912 fsck_ffs RET   close 0
> >  24912 fsck_ffs CALL  close(0x4)
> >  24912 fsck_ffs RET   close 0
> >  24912 fsck_ffs CALL  exit(0xc)
> >
> > Is this what you are looking for?
>
> Yes, thanks. Is there any 'lseek' before this write?

This is the first lseek before that write,

 24912 fsck_ffs GIO   fd 4 wrote 16 bytes
       "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
 24912 fsck_ffs RET   write 8192/0x2000
 24912 fsck_ffs CALL  lseek(0x4,0,0x290000,0,0)
 24912 fsck_ffs RET   lseek 2686976/0x290000
 24912 fsck_ffs CALL  write(0x4,0x8ad6d000,0x4000)
 24912 fsck_ffs GIO   fd 4 wrote 4088 bytes



# Han

Reply via email to