Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Carl-Daniel Hailfinger
Date: Monday, July 7, 2008 - 6:21 am

On 07.07.2008 10:07, Anton Altaparmakov wrote:

AFAICS it is not the division that fails (unless a division itself can
cause an access to invalid memory), but either the write to ts or the
read from t. Dependign on compiler optimizations, the real root cause
may be related to an access to time.

Regards,
Carl-Daniel

-- 
http://www.hailfinger.org/

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Oops with corrupted NTFS image, Eric Sesterhenn, (Sun Jul 6, 10:21 am)
Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image, Anton Altaparmakov, (Mon Jul 7, 1:07 am)
Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image, Eric Sesterhenn, (Mon Jul 7, 5:24 am)
Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image, Vegard Nossum, (Mon Jul 7, 6:03 am)
Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image, Carl-Daniel Hailfinger, (Mon Jul 7, 6:21 am)
Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image, Carl-Daniel Hailfinger, (Mon Jul 7, 6:26 am)
Re: [Linux-NTFS-Dev] Oops with corrupted NTFS image, Vegard Nossum, (Mon Jul 7, 6:33 am)