Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

BACKSPACE error 23

Hanbing_P_
Beginner
4,151 Views

       I have a program for processing data of engineering which is coded in Fortran 90. An error occurs with the 'BACKSPACE' state in the program, but I have no idea about how to fix it.

      At the beginning of the process, some temp data  has been written into a scratch 'unformatted' file,and  then I use 'BACKSPACE' to read it out in reverse. When the file pointer  almost approaches the beginning of the scratch file, an error occurs with the 'BACKSPACE' , the return value of 'IOSTAT=23' and 'IOMSG='B'' are output ! But,I do not know what this error code means.

      And there is another fact should be mentioned, I think. I have two sets of data ,nothing big difference exists between them but the amount.When I process the set of data with smaller amount, no error occurs with 'BACKSPACE'.Otherwise, it does as the way I just described.Surely, when larger amount of data is processed, larger the scratch file will be, I do not whether it matters!

     So,could anyone give me some tips about how to fix it ? Thanks a lot !

0 Kudos
25 Replies
Steven_L_Intel1
Employee
552 Views

It's a bug in the library that, it would seem, is related to how we do buffering of unformatted I/O. There isn't anything special you should do to avoid it - just use the workaround for now to allow your program to get around the bug.

0 Kudos
Hanbing_P_
Beginner
552 Views

Steve Lionel (Intel) wrote:

It's a bug in the library that, it would seem, is related to how we do buffering of unformatted I/O. There isn't anything special you should do to avoid it - just use the workaround for now to allow your program to get around the bug.

OK! Thank you ! It did work!

0 Kudos
Steven_L_Intel1
Employee
552 Views

We've fixed the bug in our sources. I expect the fix to appear in version 16, and perhaps an upcoming version 15 update.

0 Kudos
mecej4
Honored Contributor III
552 Views

The error is not yet fixed in the 15.0.3.208 update released this week.

0 Kudos
Steven_L_Intel1
Employee
552 Views

Right - possibly update 4.

0 Kudos
Reply