Hi! > > Not if you tried to do checking from ptrace monitor. > > > > And heck, yes, it is very confusing to see > > > > seek(somewhere) > > write() > > > > ond ptrace and write going somewhere else. > > Yes bugs are confusing. An application can't do this on demand so you > can't write code that relies on the effect between threads. So it would > only be a bug, not a bizare feature (that wouldn't even work on 64bit > machines). Yes, kernel bugs are confusing ;-). The "application" could be malware trying to confuse debugger, for example. The "application" could be something you are trying to debug. I did brief reading on lseek man pages, and it does not mention "kernel may seek to random place if you attempt to seek from two threads at the same time". So this is a kernel or manpages bug. Maybe you can take a look at POSIX if it permits this behaviour? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
