On Tue, 25 Nov 2003, Takayuki Matsuki wrote: > > The following is a guess what is happening. A return code on Windows includes > two codes, CR (=\n=0a) and LF (=\r=0d), compared with that on Unix/Linux OS's > which have only one code, CR (=\n). The analog is analyzing a logfile each > BLOCKSIZE (=32768 bytes which is defined in anlghea2.h) at one time so that it > may happen on Windows that the analog finishes its anaylysis at a code, CR, and > restarts its anaylysis from LF. This may be a reason why the analog reports a > corrupt line for such a line. >
You can turn debugging on to see where analog thought the line was corrupt. I doubt this is the reason, because it's supposed to treat any combination of \r's and \n's as a single new line. Of course, there may be a bug. If you can send me (privately) a short logfile to illustrate the problem, I'll have a look. -- Stephen Turner, Cambridge, UK http://homepage.ntlworld.com/adelie/stephen/ "The question of whether a computer can think is no more interesting than the question of whether a submarine can swim." (Edsger W. Dijkstra) +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
