Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Small program, very strange bug

Small program, very strange bug

Small program, very strange bug

Hi, I have got this incredibly strange bug happening with some code I've written and I fear there could be something fundamentaly wrong with (either me or) my system.

Here's the code (it's short, I promise):


#include <stdio.h>
#define FILE_NAME "sdtest.dat"

int main()
  FILE *fp;
  long idx = 0;

  fp = fopen(FILE_NAME, "r");

  if (fp)
    fread(&idx, sizeof(long), 1, fp);
    printf("old: %d\n",idx);

  fp = fopen(FILE_NAME, "w");

    printf("new: %d\n",idx);
    fwrite(&idx, sizeof(long), 1, fp);

  return 0;


The first time I run it I get the following output:

old: 0
new: 1

which increments for each subsequent run, eg.

old: 1
new: 2


old: 2
new: 3


BUT, once I have run it enough times for it to get to

old: 25
new: 26

the next run produces

old: 0
new: 1  !!!

The program can not read the file contents when it contains 26! It reads in the file contents of x"1A 00 00 00" as x"00 00 00 00"  (verified with debugging).

I have tried this same code on a Unix system at work and there were no problems, what on earth could be causing this?  Any insight/advice would be very much appreiated, thanks.

CPU:       AMD Athlon 1GHz
OS:        Win 98SE
Compiler:  VC++ 6.0

RE: Small program, very strange bug

PS. I know there's some unnecessary braces after the second fopen so you don't have to mention that.

RE: Small program, very strange bug

The text character 27 represents an escape character and as such will not read and write properly to a file in text mode. Change the read write status of the file to "rb" and "wb" then it will properly increment up to 255, once you reach there, you will need to read/write multiple bytes. The reason you did not have the problem with UNIX is it uses binary as the standard IO mode while windows uses text as the standard IO mode. It is always helpful to specify mode to make portability easier.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members! Already a Member? Login


White Paper - A Guide to 3D Printing Materials
When it comes to using an FDM 3D printer effectively and efficiently, choosing the right material at the right time is essential. This 3D Printing Materials Guide will help give you and your team a basic understanding of some FDM 3D printing polymers and composites, their strengths and weaknesses, and when to use them. Download Now

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close